I've been using KernelCare in my servers for many, many years now, and have yet to experience a single crash. One of them has been up for close to 4 years now.
I just use fallocate to create a 1GB or 2GB file, depending on the total storage size. It has saved me twice now. I had a nasty issue with a docker container log quickly filling up the 1GB space before I could even identify the problem, causing the shell to break down and commands to fail. After that, I started creating a 2GB file.
So we're getting a new console just to play AI-upscaled PS4 and PS5 "remasters"... and I suspect it’ll probably come without any support for physical media. The PS5 will be my last console. There's no point anymore.
Apple wants to make sure they get a 30% cut if you spend money on anything within their ecosystem — that's all they really care about.
There are several reports of people having their entire accounts banned, effectively losing access to everything they paid for. And it's basically impossible to get your account back.
Those aren't competitors of Spotify/Netflix; they're alternatives for people who are willing to tolerate small inconveniences to have full control over their library.
Of course it's not as easy as signing up for Spotify/Netflix, but setting them up is easier than ever (even easier for tech people).
To me, it starts to feel like work when I have to rebuild large parts of my factory because I didn't leave enough space to expand. This process feels exactly like having to refactor a bad codebase (where you feel the urge to just start from scratch).
If you plan your build properly, you can avoid this, but it takes a few runs to learn the best strategies.
Once you buy a game on Steam, you don't need to pay any kind of subscription to play it. The vast majority of games sold there are, in fact, one-time purchases. The games stay in your library even if the developer/publisher decides to delist them.
There are games like MMOs that do require a subscription, but that has nothing to do with Steam itself.
It's a great tool when you can actually read and understand the code AI is feeding you. When you don't really know how the language works or don't know programming in general, you end up getting stuck trying to guess why this valid piece of code (that looks like it should do what you asked the LLM for), is not working properly.
I had this exact experience with my workstation SSD (NTFS) after a short power loss while NPM was running. After I turned the computer back on, several files (package.json, package-lock.json and many others inside node_modules) had the correct size on disk but were filled with zeros.
I think the last time I had corrupted files after a power loss was in a FAT32 disk on Win98, but you'd usually get garbage data, not all zeros.