I still have an old laptop with a spinning disk, going almost 9 years now.
It helped me ditch Windows completely because the start-up experience for Windows 11 was just atrocious even with the smart/cached shutdown thing they're doing (I forgot the official name for it). I'm glad to see even some (un)official confirmation from this article that hogging resources at start-up is pretty much best practice in Windows land.
In Linux land today, FF and Chrome (but Chrome especially) take ages to start-up at first but system boot is as smooth as can be expected.
I thought I've made myself immune to UI bloat because, like all true programmers, I do everything on the terminal (short of browsing the web, like TRUE programmers). Until I noticed that whenever I invoke my terminal, it takes ages for the prompt to even appear, not to mention accept keyboard input.
After much frustration, I figured out that the culprit is---drumroll---NodeJS. Don't quote me on this but I think Node brought Windows best practices into the Linux terminal.
Fortunately, Linux being Linux, I managed to patch my system such that Node doesn't actually do anything unless I invoke it myself. The downside is that I have an odd script every now and then that relies on Node and these scripts would fail if I run them without having ran `node` beforehand.
It helped me ditch Windows completely because the start-up experience for Windows 11 was just atrocious even with the smart/cached shutdown thing they're doing (I forgot the official name for it). I'm glad to see even some (un)official confirmation from this article that hogging resources at start-up is pretty much best practice in Windows land.
In Linux land today, FF and Chrome (but Chrome especially) take ages to start-up at first but system boot is as smooth as can be expected.
I thought I've made myself immune to UI bloat because, like all true programmers, I do everything on the terminal (short of browsing the web, like TRUE programmers). Until I noticed that whenever I invoke my terminal, it takes ages for the prompt to even appear, not to mention accept keyboard input.
After much frustration, I figured out that the culprit is---drumroll---NodeJS. Don't quote me on this but I think Node brought Windows best practices into the Linux terminal.
Fortunately, Linux being Linux, I managed to patch my system such that Node doesn't actually do anything unless I invoke it myself. The downside is that I have an odd script every now and then that relies on Node and these scripts would fail if I run them without having ran `node` beforehand.