Nothing, unless you really want to use a DE that's still lacking behind in its adoption. There are a few tools that still only offer early support for it (like RustDesk), but otherwise Wayland is a way better choice these days. However if you got an Nvidia GPU and need to use the proprietary driver you might be forced to still use X11. Their pile of garbage still routinely bugs on Wayland, and given their work on NVK I doubt that thing will ever get fully fixed.
To my knowledge it isn't them constantly running that wears them out most, but spinning up and down very often. Weren't NAS drives designed to never spin down for that very reason?
Especially since the manpages are not written to always be comprehensible for end-users, but for developers and professionals. Some tools like tldr can help, however they rarely come preinstalled and aren't getting the attention they deserve.
Well, they arguably can also be used as one big long-term storage. Not sure who'd need to save so much data for a long time, but there surely will be at least some people who do and buy the "modern solution" over old HDDs thinking they're better in general. As the "family backup" for example, or as cold storage solution in faculties that can be quickly accessed if needed.
Read somewhere about a professor who used SSDs to "permanently" store important data on SSDs (perhaps in the comments of the article above) for a few years. Well, wasn't that permanent…
More reliable
Heavily depends. If you want to use it as long-term cold storage you absolutely should not use SSDs, they're losing data when left unpowered for too long. While HDDs are also not perfect in retaining data forever, they won't fail as quickly when left on a shelf.
Afaik KDE and Gnome do use SIGKILL at some point except for certain processes like running package managers. At least they are able to forcibly close almost anything if you really insist on shutting down now, depending on your (distro) configuration. Correct me if I'm wrong, but from my experience in Gnome you have to click on shutdown twice for it to happen, while KDE gives applications a 60 sec grace period unless you click a button in a notification pop-up.
Edit: Not sure how it is in the terminal aside from those 1:30min grace periods during shutdown.
Whatever you need to tell yourself about people voicing criticism the community culture to shut it down. I'm already contributing to the best of my abilities, so please stop with the "just fix it yourself" nonsense. Not even professionals like Torvalds would have the ability to to all that. Hell, not even companies can; System76 ends up creating a whole new DE because the cultural and structural issues with Gnome were so severe, and they're working on it for years now (arguably they could've moved to KDE, a new DE without old baggage might be a good idea though). Some parts of the Linux community even are so toxic they're famous for ripping each other apart regularly, like the Kernel devs.
It's this whole culture and the bad decisions it causes I'm criticizing. And the only way to change anything about such a thing literally is to loudly criticize it, and to introduce new people with new perspectives. Who unfortunately more often than not get alienated by all the toxicity.
You are contradicting yourself.
I already admitted my previous statement being bad.
You are looking for a walled garden that protects its users.
No, I don't. There's a difference between a walled garden and a safe environment, the word itself even says it. Windows, iOS etc. outright build closed boxes you can't escape. The Linux community rightfully doesn't like that, but to a degree where we hardly even have proper safety rails next to cliffs and either no or insufficient warning labels next to exposed 11kV powerlines. Yet we expect people who don't know what they see to not hurt themselves and instead stand still and study books for a few weeks. Even worse, in an attempt to keep answers as universal as possible the correct answers often are that "it's easy, just hook up X to the 11kV powerline" (equal to editing grub.conf, xorg.conf, or anything else that could literally kill your system or user-essential parts like the graphical interface).
I'm so fed up with the notion that any change that adds safety rails is seen as building walls. Just because you have to add "--no-preserve-root" to delete your root folder you're not prevented from destroying your OS if you want to (people seriously argued against this change). Improving the apt warning so humans pick it up is not a wall either.
Just criticizing a toxic culture that causes systemic problems. It's both sad and funny you still think I'm the one with the problem though.
Should've been more verbose with that argument.
Yes, there was that single safety measure. Will this single thing with the white text next to hundreds of other rows of white text create sufficient awareness to discourage someone who was 1. told by the internet that "this is the solution!" and 2. has no notion about the severity of this action given they've nothing to compare it to except systems (and the web) that constantly cry for attention? Lol no, absolutely not.
There's a good reason fatal warnings are almost always red or yellow and there are literally pictograms of human skulls in warning signs. People will not understand some white text next to a ton of other white text (that's utterly incomprehensible to most of them, raising the tendency of people to disregard all of it) paired with something akin to a captcha as the fatal warning it was meant to be. That is not how (a majority of) humans work. The warning as it was back then provided no sufficient safeguards for newcomers, yet gave people sufficient reason to blame them. Although, and that's the worst part, they have to be applauded for even featuring a warning at all.
The argument that came up afterwards was about exactly this, making the warning adequate and sufficient so even if the information on the internet said they should execute this, people are still being made sufficiently aware so they're more likely to stop despite feeling that whatever they want might be just around the corner. But of course there'll always be some people who prefer to call others stupid for their lack of experience or mistakes, especially if they want to protect something from criticism they identify with.
My previous statement was bad, but I stand with the opinion about the whole debate from back then being a good example.
No, I am the fire department for my family who're currently moving over to Linux and are already fed up with the communities' toxicity and unhelpful nature in most corners of the internet. And I can't blame them, it's an awful experience. The self-righteousness you're putting on display with your comment is part of the problem.
Linux users don't trust telemetry, but sending useful information first try is hard too.
Let the apologists have a field day in the comments.
For anyone interested in the first article, it's on wccftech.com. For the second one we assumeably have to wait yet another year.
If someone posts AI slop memes, help ratio them.