Well LLM's cannot transcode perfectly correctly, so the fact that Rust has lots of static checking is really important. Not just for memory safety - Rust helps with many other classes of bugs too.

> then using Rust may just make the bug soundless, because the language runtime/code-gen "avoided" usual punishments that might make the bug (and bug report) obvious.

I think what you're saying here is that LLM's often cheat to solve the immediate error, e.g. by using `unsafe` where you really shouldn't, or just making a test not test anything. That's definitely possible.

Clearly you've never bought a TV or headphones!

There are plenty of manufacturing tasks that are still done by humans because it's too much hassle to make a dedicated robot to do it. Even on high volume car manufacturing it's very common to have human steps.

Sorting is just where they've got to so far; not the final destination.

Still, I expect it won't matter - by the time we have reasonably priced robots that can reliably do all housework, that's like 90% of jobs eliminated from society and probably society will collapse.

For people who don't have a choice, type checked Python is better than nothing.

You pretty much only had people you actually knew as friends. People posted photos and messages about real life. No sharing of posts, memes, few stupid people. It was great.

We'll probably never get that back.

Sure they can. If Google loads and Github doesn't, then it's clearly Github being down, not the mobile network.

Also not everyone uses a phone. My desktop & fibre internet has way better than 99% reliability.

Also I couldn't see any explanation of what happens when a network request fails. That's a huge downside of local rendering.

I think for most sites the best option is still server-side rendering but use a fast backend (e.g. not Python) and lightweight frontend.

I dunno, that's the best I can do for now. Maybe you can do better?