Casting Out Daemons
It's a new computer, and it's also a chance to try out a new vendor.
I gave my first daughter the best computer I had. This nice, lightweight tablet with handwriting recognition will help her record her lab experiments.
I'm fed up with some vendors and their vendor-provided management software. Nothing irritated me more than to find that my issues with their code and their bulky system restoration systems were echoed time and time again in countless Internet postings.
Let's see, there's a service that checks for updates. There's one that collects management data. Please! I don't want to lose 10-plus-per cent of my processing power to intrusive services! And when those remote support services are found to have big security holes, why do I want to add those patches to all the others?
Then there's the bulky vendor-specific help and support file that needs downloading. The overlly bulky system restore that takes two or more DVD's and overnight to complete the process, through multiple and mysterious reboots.
No, it's time to tell computer vendors to lighten the [system] load. Need remote support abilities? Don't code up a backdoor, use Remote Assistance. Why do hardware drivers need updates by you versus having the user use the hardware vendor site?
Nah, I'm not feeling it anymore. Windows machines call them Services, but we with a *NIX background call them Daemons, beneficial helpers to system running. But after living through them and hassling with their risks for years, I'm casting them out, same as their less beneficial cousins.
My current vendor doesn't issue updated hardware drivers. Those are on Windows update, didn't I know, or on the hardware vendor's website. I think I'm going to like this laptop.