| I can't answer your question philosophically. You could decide not to, and accept the bugs as natural limitations of what's available to you. But from a tech perspective, I see minor annoyances caused by complex systems with parts from many companies where 1 error in coordination can have very large bad consequences (ex: losing the Intel Serial IO on the Fold due to errors in the Intel drivers = no bluetooth, no touchscreen, so you will think it froze while it just needs the drivers reloaded, say by doing that from a USB keyboard or by RDP) Our current hardware is great, and never has been simpler to use, but it has also even more complexity than before: this is increasing the risk of subtle issues that even most readers of HN would have no idea about if they hadn't read first about it here (like Dells catching fire due to ACPI S0 idle). But nothing is set in stone! You did that in the 2000s? You can still do that if you want a great experience! You may already know about tweaking IO and IRQ addresses from before? That's not very applicable anymore, so update your knowledge to today's problems: learn about the the DSDT, the default APST settings per device, etc. It may take some time. However, once it's done, 1) you have a much finer understanding of how your computer works allowing fixing the root cause, 2) so the problem rarely comes back but if it does you are ready 3) you're ready to tackle more challenges! This year I'm moving to Linux on the Laptop using arch. Everything I learned on Windows is extremely helpful. The rest, I'm learhing it along! |