Long time "old-school" kernel maintainers don't know Rust and don't want to learn Rust (completely fair and reasonable). But some of them don't want to work with the Rust guys for lots'o'technical reasons.

It's by far not an easy situation technically. Like this is a huge challenge.

But some of those old-school C guys are being vocal about their dislike of Rust in the kernel and gatekeeping the process. This came to a head at a recent conference (Linux Plumbers Conference?) and now one of the Rust maintainers has quit.

The big technical challenge is being confounded by professional opinions.

You live in a fantasy world if you think it's possible to catch 100% of mistakes internally.

Nice strawman. No one said anything about catching 100% of mistakes internally. But outsourcing that work to unpaid volunteers with zero verification of qualifications is the definition of "passing the buck".

The correct answer is to hire and train up a QA team.

I have it on good authority that pedos and criminals drive cars and eat food too! We should do something to those facilitating that.

No, because it isn't 2015 anymore.

That would break 90+% of installations then. And all of Azure.

Last I'd heard other options either didn't have infrastructure to charge vehicles on long trips

Literally isn't an issue going forward. Other EVs can use Tesla chargers.

They're already talking about breaking up Google/Alphabet

But it could also be for legal reasons, like websites where you can post stuff for everybody to see, in case you post something highly illegal and the authorities need to find you. Another example is where a webshop is required to keep a copy of your data for their bookkeeping.

None of these require your account to "exist". There could simply be an acknowledgement stating those reasons with "after X days the data will be deleted, and xyz will be archived for legal reasons".

Mostly it's 30-90 days where they keep your data, just in case somebody else decided to delete your account or you were drunk or something

This is the only valid reason. But even then this could be stated so that the user is fully aware. Then an email one week and another one day before deletion as a reminder, and a final confirmation after the fact. I've used services before that do this. It's done well and appreciated.

This pseudo-deletion shadow account stuff is annoying.

What the user was doing is that they don't trust that the system truly deleted the account, and they worry it was just deactivated (while claiming it was "deleted"). So they tried to do a password recovery which often reactivates a falsely "deleted" account.

I've done this before and had to message the company and have them confirm the account is entirely deleted.

I feel like nowadays there's less forums or places people can ask help with

I'm sorry, what??

There are more places than ever to find support. The Ubuntu forums, EndeavourOS forums, Manjaro forums, NixOS forums, SUSE forums, etc. Just about every larger distro has it's own forum and they're all very active. Then there are general Linux, Linux "newbie", Linux help communities on the various Lemmy servers and (whether you like it or not) on Reddit also. Then there's Mastodon. General tech forums like Level1Tech, Hacker News, etc.

Why should Amazon be liable for stuff sold by third parties?

Even when proven dangerous products are reported to Amazon they continue to sell it.

Louis Rossman talks about it a lot.

https://youtu.be/eS698R-bxuc

JSON data within a database is perfectly fine and has completely justified use cases. JSON is just a way to structure data. If it's bespoke data or something that doesn't need to be structured in a table, a JSON string can keep all that organized.

We use it for intake questionnaire data. It's something that needs to be on file for record purposes, but it doesn't need to be queried aside from simply being loaded with the rest of the record.

Edit: and just to add, even MS SQL/Azure SQL has the ability to both query and even index within a JSON object. Of course Postgres' JSONB data type is far better suited for that.