Instead of having a post which is obviously a "Third" Alpha post, I've now decided that we should begin with the first of the beta posts, which will start to make everything come together to the point where it will eventually make it become the ultimate post - The Culmination of the Majority of My Research of a thing which I intend to only have my knowledge be for the present - & For Everyone else to just find out.
We will consider the answer to a few questions during this discussion:
- What, exactly, am I talking about whenever I say that this "thing" is supposed to be something that I only personally know about for the present time, and why "everyone else" should find out after much of it is said & done?
- Why do I feel that "If I use the most popular, and most trusted OS made by a company in Redmond, Washington, U.S.A," that I blame the software in the event something does go wrong, but if I use something compiled by a bunch of hippies and distributed on the Internet for free, I blame the hardware instead?
- What if when I choose to use my new OS instead of Windows, I run into reliability issues?
Let's look at these questions, one at a time. Starting with the first one out of the series of 3.
1. What exactly am I talking about whenever I say that this "thing" is supposed to be something that I only personally know about for the present time, and why "everyone else" should find out after much of it is said & done?
I have long held that the knowledge that I have assembled from research during much of the latter half of December 2022 wasn't really ready to be revealed to anybody just yet. And, if I had revealed my plans to people who could try to talk me out of it, then I would ultimately abandon those plans and never touch the idea of such things again with a 10 foot pole or even a 39 1/2 foot pole. Never mind my hands being mere inches away from such things.
Also, the idea that I would personally sanction closed-source offline software platforms, such as Microsoft Windows in favor of more open source things from versions 10 forward ended up becoming rather unpopular with many computer geeks - but you have to realize, that many versions heading forward from Windows 10, and to even further forward Windows versions will ultimately NOT be remaining the same Windows versions in essence taking advantage of the x86_64 architecture like was popular during the latter half of the 2010s and much of the 2020s, or even the i686 architecture which has been popular since the 1990s, and the 8 and 16-bit Windows which had been developed from 1985 - 1995.
The truth is, that I also don't buy the marketing. Like who cares if the marketing that Windows offers is that it's popular & I should consider only buying into that marketing?
Popularity doesn't necessarily mean it's something worth the value of the license key. Popularity means that it's the thing which the most people jump ON the bandwagon of. On the other hand, I'd rather be the one that jumps OFF the bandwagon. It's crowded on there anyway, and I actually don't want to go to wherever the bandwagon's going to be headed --- considering the destination is likely somewhere where I don't want to be.
2. Why do I feel that... "If I use the most popular, and most trusted OS made by a company in Redmond, Washington, U.S.A.," that I blame the software in the event something goes wrong, but if I use something that was compiled by a "bunch of hippies" & distributed on the internet for free, I blame the hardware instead?
Well, I believe that mainstream popularity is obviously overrated. Like, who cares if mostly everybody and their dog runs Microsoft Windows systems? Windows as an OS, especially in the later versions - particularly after Windows 7 has become less of a quality experience, and more of a royal pain in the rear end. Why? Well, consider these few things:
Exhibit A: Blue Screens in XP, Vista, 7 vs. Blue Screens in 8, 8.1, 10 and 11.
On top of this picture, we see the Blue Screen of Death in Windows XP, Vista, and 7. On the bottom of this picture we see the blue screen of Windows 8, 8.1, 10, and 11 (although 11's Blue Screen is now black which makes it more accurately a "death" screen.)
Now, displaying the stop code in the XP - 7 BSOD was a better idea as opposed to "You can search for the error online: INSERT THE STOP CODE THAT CAUSED THE ISSUE HERE." Why? Well, let's be realistic. Suppose that the Windows post-7 device was "the only device." Well, unless you searched the code online using your cellphone or tablet if it could utilize such a capability, you're pretty much forced to have the device repaired - and of course, since we live in a world where "Time is money" literally anything that could have the device which could be used for any productivity purpose down for even merely but a moment will likely be spending time trying to have the actual broken device fixed to a last save state or probably a bill with the repair technician.
Windows in my opinion --- if we lived in a perfect world, would either not exist at all, or would be the absolute most stable OS on the face of planet Earth, to where nobody would have ANY reason to use anything else but Microsoft Windows. So, if something goes WRONG with Windows, then by all means, I'll blame Windows every. single. time. Because many of the versions after 7 seem more rushed - and of course, with the disinclusion of an ad-free Solitaire game by default out of the box, makes it even less desirable of an overall experience for me.
Reality Check! We don't live in a perfect world. And Windows has never been, never was, and never will ever be a perfect OS for 100.0% of humanity to use on their devices --- especially if it's going to continue to have these issues which have been more or less common since the 1990s.
Oh, by the way... Another thing I'm going to mention. Trusted Platform Module and Secure Boot aren't security devices that really secure the device. They are just things Microsoft forced to have Windows 11 as a requirement so that hardware as old as Core2Duo wouldn't even touch Windows 11. So, I have plenty of reason to blame the hardware if something should just so happen to go WRONG.
Exhibit B: The fact that Linux is absolutely not an annoying ecosystem that demands everything be part of a device ecosystem.
Since my first day using Windows 11 back in February 2022, I have never done one thing: That is... Use Microsoft Edge. Why, you may ask me? Well, Microsoft Edge is not an Internet Browser that I want to rely on, for anything. If anything, it will become the successor to the Browser that it replaced from Microsoft ---- Internet Explorer. So, yeah. Edge is now the new "Internet Explorer."
Also, if hardware doesn't work, then the software will obviously at least basically tell me what's wrong. No codes - because I don't need cryptic nonsense like this in my life.
Besides, most hardware will work with non-proprietary drivers out of the box in Linux anyway - of course, the rare time that does not hold true, proprietary driver activation usually tends to work easier than trying to get proprietary drivers to activate in Microsoft Windows.
3. What if I decide to choose my new OS instead of Windows, & I run into reliability issues?
First of all, what "reliability issues" are we talking about? I mean, I've noticed when something ran Linux it ran absolutely like a clock and always started up whenever I pressed the power button.
In some cases, such issues can be fixed with a re-install. Others? Rebuilding or replacing the hardware might end up having to be what "the doctor ordered."
My point? My new yearly motto isn't just going to be some random nonsense that I pulled out of my rear end. No, no. But it will be a personal mission statement that I not only live by, but continue to follow, during the next few, and eventual twilight years of the 2020s decade, which could be the years where all religion is eventually abolished in the name of "Government" providing everything and all things.
No comments:
Post a Comment