Core parts of the product, like navigating to individual files in a code review, are broken

Edit: Never mind, found it https://www.postgresql.org/docs/19/pgplanadvice.html

And no, ECC is relevant with less than 64 gigs of ram, there's a reason it's been a standard on servers since the 90s

They're great for hobbyists but people on here keep bringing them up as the flagbearer of euro hosting

More often than not they're running on a VPS, and cloud providers have been pushing the envelope of what a vCPU is. Amazon still bills hyperthreads as a single core!

Add to that their servers are often aging and you get a recipe for slow web services

I feel like the programming community is very different than in the early 2010s – when's the last time you've seen a coworker brag about using vim – but I can't really put my finger on what changed exactly.

I really dislike this rhetoric, you sound like the FSF guys who are like "you're not free until you're running coreboot with zero binary blobs". Sure they have a point but also, most people are fine running regular linux.

No one here is saying C is a great design, but in the context of 60 years ago, it worked out pretty well, and all the language which had additional runtime complexity (Pascal of course, but also Ada and FORTH) struggled because they didn't dial the right level of complexity

Sum types aren't the be all end all to all issues, for example you can not representer pointer values efficiently with sum types. Even rust does not wrap up pointers with sum types. Now try to go back 37 years to C89 and ask yourself if they were going to require compilers to have stringent checks like the rust compiler does.