Even if the software was perfect, virtually all desktop RAM isn’t ECC equipped, so you potentially have even the hardware corrupting the state and requiring restarting because of that.

Switching from Xitter to bluesky (or anything else) is much much much easier than emigrating.

Both mentioned games are notorious for the scale of the issues at launch, and the resulting backlash. NMS for the lack of content and Cyberpunk for the huge amount of bugs.

They both had a lot of issues at launch

And how is calling conservatives “weird” how you describe?

Compared to conservatives calling anything left of them “communist”, calling a party backing a felon president and a vice president that can’t even make small talk at a doughnut store “weird” is very fitting.

My point is that SQL works with and returns data as a flat table, which is ill fitting for most websites, which involve many parent-child object relationships. It requires extra queries to fetch one-to-many relationships and postprocessing of the result set to match the parents to the children.

I’m just sad that in the decades that SQL has been around, there hasn’t been anything else to replace it. Most NoSQL databases throw out the good (ACID, transactions, indexes) with the bad.

The fact that you’d need to keep this structure in SQL and make sure it’s consistent and updated kinda proves my point.

It’s also not really relevant to my example, which involves a single level parent-child relationship of completely different models (posts and tags).

SQL blows for hierarchical data though.

Want to fetch a page of posts AND their tags in normalized SQL? Either do a left join and repeat all the post values for every tag or do two round-trip queries and manually join them in code.

If you have the tags in a JSON blob on the post object, you just fetch and decide that.

Fireworks are art. Art isn’t inherently wasteful.