I’d say both local data structures and algorithms atop them, and external services like DBs, etc., are both just “resources” in a more abstract sense. Optimizing performance is a matter of using the right resources for the right things. Algorithms help a lot when you’re building FE components (even if the server is rendering them, or “rendering” responses for the FE).
I’d also argue “micro-ORMs” like Diesel (which isn’t really much like ActiveRecord, Hibernate, etc., but more a very thin DSL/interface that maps SQL types to Rust types), combined with LLMs, are the ideal solution (assuming we still want humans to be able to easily understand and trust the code generated). And there’s a big argument to be made for schema migration management being done at the app level (with plain SQL for migrations).
All that said, at work, we use Rails. And ActiveRecord’s “includes/preload/eager_load” methods are fantastic solutions to 99% of cases of querying for things efficiently, and are far more clear than all the SQL you’d have to write to replicate them.
I’ve only taken two buses in Brazil (Goiânia to Pirenópolis and back), and can definitely report that this was not the case there. It was incredibly hot and dry there until you hit the mountains, and the AC barely worked. Granted, I think this was one of the crappier bus lines, and they had a monopoly on this particular route.
There’s an entire Linux distro (Asahi) for MacBooks. Apple has never released a Mac with a locked bootloader.
And macOS frankly provides a far better Unix experience than ChromeOS, in my experience, having actually used both (including for development, though only for a short time on ChromeOS because it was horrible).
Apple did not lock the bootloader, but they do not provide documentation for their products.
What would have been a trivial porting work with documentation, becomes extremely time-consuming and hard work without documentation.
That is why Asahi Linux lags by several years with the support for Apple computers, and it is unlikely that this lag time will ever be reduced. Even for the old Apple computers the hardware support is only partial, so such computers are never as useful for running Linux as AMD/Intel based computers.
This is what I built Jonline for. Haven’t maintained it for a while, but it’s quite functional as-is. Basically a very vanilla Twitter/Reddit-with-first-class-calendar-events, standard Rust web+gRPC server on Postgres DB, React web UI, and no encryption other than HTTPS/TLS. No server-to-server communication, just username/password auth. Super easy to understand APIs (https://jonline.io/docs). (I do need to build better cross-server auth, but this can be done in the FE only with the existing APIs.) Can boot it in a Docker container in seconds. A few “demo” instances I run are linked from the Readme: https://github.com/JonLatane/jonline
We definitely don’t have any hard boundaries baked into this tech preventing big tech from (ab)using our data this way. But are there specific companies you think are doing this? I think with Meta products, it’s been rather obvious for a long time. But I’ve had a Nest doorbell camera and thermostats for years, and first iRobot and now Roborock vacuums, and they don’t really seem so suspect.
You should assume that Google is collecting every scrap of data they can from nest products and that your data will (or could) be handed over to police and the state with or without warrants and with zero notice to you. There were concerns raised with irobot devices selling the floorplans of your home (https://gizmodo.com/roombas-next-big-step-is-selling-maps-of...) and now its owned by China (Picea) so who knows what they're doing. Roborock is also a Chinese company who appears to have been under investigation in Korea for data leaks (https://koreajoongangdaily.joins.com/news/2025-03-05/busines...).
At this point I'd consider anything not locally hosted (and certainly anything owned by Google, Amazon, or facebook) to be highly suspect.
I guess the flipside of this is, do we want poor/homeless people from groups our society dubs “overrepresented” to only be able to find help from organizations that specifically serve selected “overrepresented” groups? Are there no obvious bad sides to that?
Because you can’t really have the one without the other.
I’d also argue “micro-ORMs” like Diesel (which isn’t really much like ActiveRecord, Hibernate, etc., but more a very thin DSL/interface that maps SQL types to Rust types), combined with LLMs, are the ideal solution (assuming we still want humans to be able to easily understand and trust the code generated). And there’s a big argument to be made for schema migration management being done at the app level (with plain SQL for migrations).
All that said, at work, we use Rails. And ActiveRecord’s “includes/preload/eager_load” methods are fantastic solutions to 99% of cases of querying for things efficiently, and are far more clear than all the SQL you’d have to write to replicate them.
reply