Remind me the another recent post: You should write an agent https://news.ycombinator.com/item?id=45840088

Some years ago I read about a system to store solar (heat) energy in a well during the day (by warming water and pumping it down), and retrieve it by night. But haven't heard anything since - did anything become of this plan?

What's wrong with tokens in local storage?

Anyone who is looking at using SQLIte + Rails should check out the work done by Oldmoe (X/Github) on his Litestack project.

Here's the intro paragraph: "Litestack is a Ruby gem that provides both Ruby and Ruby on Rails applications an all-in-one solution for web application data infrastructure. It exploits the power and embeddedness of SQLite to deliver a full-fledged SQL database, a fast cache , a robust job queue, a reliable message broker, a full text search engine and a metrics platform all in a single package."

I'm currently using it on a project and can't say enough good things about it!

https://github.com/oldmoe/litestack

No, you can set up replication with, eg LiteFS where you have one writer and multiple read replicas.

That said, then you have operational overhead that defeats a part of the purpose with SQLite. In practice, you can get very far with a single machine and many CPUs (Postgres is ironically a good example of this). In eg Go you can easily parallelize most workloads. In rails, I don’t know if that’s possible. A quick search suggests there’s a GIL which can be limiting.

What's the opposite of the UNIX philosophy?

I’m not going to trust a project like this – made by and for one company – with production workloads.