Just checked and my most recent document is a diagram of data flows between two services.
Highly recommended.
Or are you worried about people stealing and making pirated copies?
I know you could make the argument “the right license wouldn’t allow that”, but that would only be enforced if you follow up through the courts, perhaps internationally. I just can’t be doing with the hassle unfortunately.
There’s a ton of work that’s OSS. There’s also a ton of work that’s not.
This is a tool that I’d happily pay double the amount that they’re asking if it was OSS. I also regularly fund OSS maintainers.
Heck I’d even be fine with a closed source by default, but pay to get source code access too.
As to pricing, I need to be able to financially justify the time spent working on the app, and the price is one that I hope will let me do that.
Will be upgrading in the future, congratulations on the launch!
- Storing results for scientific research
- Local analysis of data exported from server-based databases
- Experimenting with database designs before exporting SQL to codebases
- Maintaining relational data where a website or app are not needed (eg. tutors keeping client records)
- Recovering data from databases used by other products (eg. phone backups, discontinued apps)
> So crap filtering became important. Businesses were built around it. Some of those businesses came up with a clever plan to make more money: they poisoned the well. They began to put crap on the Reticulum [internet] deliberately, forcing people to use their products to filter that crap back out.
When I'm in a tinfoil hat sort of mood, it feels like this is not too far away.
EDIT: There's more in the book talking about "bad crap", which might be random gibberish, and "good crap" which is an almost perfect document with one important error in it.