Linux Is Best on Nostr: > What's your opinion on tiny10/tiny11? Use with caution and backup, often. The ...
> What's your opinion on tiny10/tiny11?
Use with caution and backup, often.
The problem with customized builds of Microsoft Windows is twofold (2 issues). 1st, you have to worry about every Microsoft update or patch breaking this customized build. Or assuming nothing breaks, you could just as easily end up with the same bloated system you were trying to avoid, with the next unsuspecting update, thus defeating the purpose of using the custom build.
The 2nd issue, is simply, unlike Linux where I can easily review everything. This is Windows and there are so many embedded features, apps, services, files, etc... Would you even notice if I snuck something in? I recall the days of everyone using "Windows Black Edition" which was Windows with a lot of pre-installed drivers, firmware, apps, and other "goodies". You could warn people until you were blue in the face, that it was infected, but people would ignore such claims as "false positives" - They were not false positives and if you knew what you were doing, you could locate PCs remotely using "Windows Black Edition".
My point being, I am always uncertain about customized Windows ISOs the people make. It's a lot easier for something to go wrong, either through normal usage, or through some sneaky bad faith individual or group.
A bonus issue, which even I almost forgot before submitting this, is that sometimes security updates from Microsoft Update are integrated. By that I mean, the update may claim it addresses "X, Y, Z", but it also, unknowing to yourself, fixes "1, 2, 3". You may skip that update, because your custom build does not have "X, Y, Z", but it does most certainly have "1, 2, 3" and now you're missing out on that fix. I suspect Microsoft does this partly to save time, partly because they don't always document everything publically, and partly I would not be surprised if they did it to punish people who tried to "pick and choose" updates. Another reason, why I much prefer, Linux, of course.
Use with caution and backup, often.
The problem with customized builds of Microsoft Windows is twofold (2 issues). 1st, you have to worry about every Microsoft update or patch breaking this customized build. Or assuming nothing breaks, you could just as easily end up with the same bloated system you were trying to avoid, with the next unsuspecting update, thus defeating the purpose of using the custom build.
The 2nd issue, is simply, unlike Linux where I can easily review everything. This is Windows and there are so many embedded features, apps, services, files, etc... Would you even notice if I snuck something in? I recall the days of everyone using "Windows Black Edition" which was Windows with a lot of pre-installed drivers, firmware, apps, and other "goodies". You could warn people until you were blue in the face, that it was infected, but people would ignore such claims as "false positives" - They were not false positives and if you knew what you were doing, you could locate PCs remotely using "Windows Black Edition".
My point being, I am always uncertain about customized Windows ISOs the people make. It's a lot easier for something to go wrong, either through normal usage, or through some sneaky bad faith individual or group.
A bonus issue, which even I almost forgot before submitting this, is that sometimes security updates from Microsoft Update are integrated. By that I mean, the update may claim it addresses "X, Y, Z", but it also, unknowing to yourself, fixes "1, 2, 3". You may skip that update, because your custom build does not have "X, Y, Z", but it does most certainly have "1, 2, 3" and now you're missing out on that fix. I suspect Microsoft does this partly to save time, partly because they don't always document everything publically, and partly I would not be surprised if they did it to punish people who tried to "pick and choose" updates. Another reason, why I much prefer, Linux, of course.