Hacker News new | ask | show | jobs
by 3dfan 1664 days ago
It seems to be a universal law of software projects:

1: Start out lean and simple. Often replacing an old complex one

2: Become more complex over time

3: Be replaced by a new lean and simple one

2 comments

If anything, this behavior is far simpler than trying to automagically coerce types and marshal differing types to/from one column.
I think the point here is that there are now two modes of operation, which leads to more complexity overall.
Strict tables still do both of those things.
I think this is a concerning pattern when the core usage of the software gets more complex due to the new features.

If you can take a developer using the old version that was lean and simple, give them the latest version full of extra features, and they can use that version without any need to change anything, then I think it's fine.

And, so far, I think that SQLite has done a good job of keeping their core usage lean and simple.