FWIW “Deceptive Pattern” is still fitting, both in meaning and tone.

Depends on what you mean by “hardware”. Most microcontrollers can’t. There are a bunch of ancient processor architectures that modern Linux doesn’t support either, and more esoteric setups that no one has bothered to port Linux to.

Rust, IMO, provides a set of convenient features (borrow checker, RAII, generics, sane operator overloading, opt in unsafety) while leaving out ones that get pretty invasive and are hard to use in an embedded context (exceptions, new/delete operators, GC).

I’ve never seen it used outside of OpwnWRT. I assumed they made it specifically for it.

I’ve heard of some cases where the Linux port of a game is so bad that running the Windows version with proton ends up working better.

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.

Are they using the beta v555 Nvidia drivers? I, and a lot of other people, are having a lot of issues with the current stable ones not supporting implicit sync.