This (and the concept of extinction credits) is an opening plot point in the book “Venomous Lumpsucker”, which I found a good read.

Quick examples:

  - Inversion tillage (ploughing) to bury green manure crops or bulky organic manure
  - Subsoiling (deep tillage) can help break underground compaction, to allow better root penetration
  - Working with soils prone to surface capping

  - Full inversion tillage
  - Low/min-till
  - No-till

EDIT: This is a response to the question "why do it?" rather than anything in the context of the article itself.

> 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.

Just checked and my most recent document is a diagram of data flows between two services.

Highly recommended.

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.

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.

  - 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)

Since Tahoe is likely to be released in the next month or so, I judged it better to start with Sequoia and keep it supported rather than start with Sonoma and risk needing to drop it shortly after launch.

For those who’ve not seen it already, there’s a good guide on when to use SQLite here: https://sqlite.org/whentouse.html

This is a bit of a shift, but the numbers aren't really stable yet so it's hard to tell if it'll stay there.

Auto-enabling foreign keys absolutely should be an option. I'll make a note of it.

I don't know about auto-loading extensions though. Will have a look. That might not mix well with the App Store rules and I'm reluctant to let the direct/app store versions drift apart in terms of features.

It's unlikely that I'll add a form builder or report generator to the app. I don't want it to grow until it can send email.