Theme switchers! My favorite example of why "document-only" sites might need JS. Sure, you can use @media prefers-color-scheme for defaults, and you can do checkbox/radio shenanigans to make it switchable, but there's no way to persist that preference on a static site without JS.
If you don't care about your site being static then you can track it server side, but that has big implications for his you can just your site. Sticking a little flag in localStorage really is the best solution, if you can get past ideological purity.
Good example. There is simply a long tail of things that are valuable to static sites that HTML can't/won't provide. Some other examples from my simple blog:
- Using buttons/links to seek to specific times in a
Not the person to whom you responded, but several times I have been dealing with debugging. Issue, tried. Opus/Sol/whatever and come up dry, then thrown it at Fable and gotten the solution in one shot.
The corn-syrup comment made sense to me FWIW. I associated corn syrup with mass-produced food that's optimized to make all your taste receptors go "bling" when it first hits your tongue, but lacks any real substance. Which also describes the text that comes out of an LLM.
DuckDB is heavily focused on analytical workflows, so it stores data in a compressed columnar format. So "rewrite one row" is more efficient in SQLite, but "sum all the values in this column" is vastly more efficient in DuckDB.
That's the core of the difference, to me. But the projects also have a pretty different ethos. SQLite has always prioritized simplicity, often at the expense of features, whereas DuckDB's approach to features seems to be "the more the merrier." E.g. the star feature of this new release, client/server mode. Plenty of people would love to see something similar in SQLite, but it doesn't seem likely.
Feed aggregators (inoreader, feedly) make this difficult, though. One request may end up serving any number of end users, so you can't personalize ads the same way.
Good, you might say, and I wouldn't disagree, but Google et al sure would.
If you don't care about your site being static then you can track it server side, but that has big implications for his you can just your site. Sticking a little flag in localStorage really is the best solution, if you can get past ideological purity.