@Davey:
While your suggestion is legit, most people will NOT buy used equipment. They won’t even buy used equipment from loved ones. Even those that might buy used equipment, may not have the know-how to replace a motherboard and CPU. So while this is a legit option, it isn’t an option for everyone. I never said that D3 would stop supporting Win 10. I’m talking about the end of life (EoL) of Win 10 coming from Microsoft. EoL does not mean on the EoL date that Win 10 PCs won’t boot. Here is what Microsoft is saying
What is Windows 10 end of life? End of life and end of support are terms that refer to the end of technical support and security updates for Windows 10. After 10 years, this older version of Windows will no longer receive free software updates from Windows Update, technical assistance, or security fixes.
There is an option to pay a small fee to extend support of Win 10, but this amounts to kicking the can down the road aka procrastinating. An important issue to consider is if the incoming US president makes good on his word to impose tariffs, this could raise the price on a lot of electronics (PC equipment), which could make buying new or upgrading an unavailable option. If one can’t buy new and won’t buy used, then the Linux option becomes more attractive.
Please do not be confused with D3/D4 requirements and the End of Life of Win 10 coming from Microsoft. As of right now no one can guarantee what Microsoft will do on the EoL date or after the EoL date. As stated in a prior post above, Microsoft crippled Win XP to force customers to move to Win 7. It was very effective. M$ might not take this same tactic with Win 10. However, they could gradually make Win 10 work less and less efficiently. Win XP is not the only software package/product that M$ has forced into obsolescence.
You said:
Yes I do and the thing is every time. Microsoft comes up with a new OS. People go off the deep end. I have been using windows from 3.1. From windows 95 to windows 11. It basically the same foot print.
False. It is not the same foot print. Not even close. If you mean foot print as in the amount of physical space required for clean install, then you are very wrong. The Win API alone ballooned between the late 1990s and early 2000’s. How do I know? The release of DOT Net API, the various DOT Net enabled programming languages, and the interoperability layer between the raw C based API, the C++ MFC, the DOT API, and the interop layer. No sir. The OSes have changed a lot. Win 10 is a major break from operating system products to a full on spyware platform masquerading as an operating system. Win 11 extends the spyware, tracking, and data leaking with supposed Ai components. Welcome to having a smartphone, spyware platform on your desktop. The only entity going off the deep end is M$, who decided to dump this spyware platform on the public. Don’t take my word as the truth, go ahead and google what the Win 10 Photoviewer app does. Here is a hint: it leaks like a sieve. Keep in mind that M$ can back door their way onto your system when ever they want and they demonstrated it:
- a windows update changes and reverts user settings
- the public screams foul, WTF, how/why are you changing my settings?!.. its suppose to be a software/OS update
- M$ goes “opps… my bad I’ll just go in and change those settings back”
- the public screams bloody murder
- M$ ignores the public and changes user settings anyway
- lots of anger and fuming by the public along with mumbling under their breath
A few folks quietly migrated to Linux. There remains loud groans every 2nd Tuesday of every month (window update Tuesday).
Again, do NOT trust what I say is the truth. Go to google and search “public outcry after Microsoft changes user settings with windows update” without quotes, and see for yourself.
@Slothic:
You said:
Install AtlasOS. Just don’t use it as your daily driver and you’ll be fine.
Remove TPM 2.0 Requirements from the Win11 installation media, you can do this using Rufus.
Quit gaming, go outside begin to touch grass again.
Your suggestions are horrible, dangerous, and would leave those who follow your suggestions, vulnerable to viruses and other types of malware. Please do not make such suggestions. Instead of listing and delving into all of the details of what is wrong with AtlasOS, I’m going to point everyone to Brodie’s video:
- Watch this video before using Atlas OS Windows (Historical) ==>
https://www.youtube.com/watch?v=ctONKQByx-M
Brodie’s video is in response to a Linus Tech Tips video, where Linus gives dangerous advice to his audience without doing the research. I never advise folks to take unnecessary risks like installing software that is going to drastically modify the Windows OS. This is a very big no-no. I consider your recommendation to be like encouraging someone to engage in unprotected sex, with a stranger, in a one-night-stand scenario. This is going to walk folks directly into harms way, regardless if harm reaches them or not. This is Linus’ video (please don’t follow this advice) ==> https://www.youtube.com/watch?v=dc7CIkZcWYE. The advice offered falls squarely in the category of malicious trolling. This isn’t funny at all.
You said:
As a Linux and Windows super user, I’ll recommend AGAINST migrating to Linux.
I doubt the sincerity of your statement, because of your horrid suggestions. I don’t think you are a Linux user. I seriously doubt you daily drive Linux for greater than 30 contiguous days, for daily tasks and gaming (personal use), where you use Linux for more than 4 hours per day, and its 4 hours not in a broswer. I seriously doubt you do any online shopping in browser on Linux.
I’m aware of the LinuxCast video. I have strong disagreements with how he classifies things, his over generalizations, and broad statements. Matt @ LinuxCast should know better than to the paint the community with a broad brush even when citing reddit and mastadon posts as examples. They don’t represent the entirety or the vast majority of the community. Matt makes a reference to issues Nvidia GPU users experience with Wayland. He classifies this as a Linux pain point, but never fully explains the situation. The Nvidia/Wayland issues are not Linux caused problems, these are problems caused by Nvidia. Matt does not explain the back story of how Nvidia corporate management has deliberately chosen to take a contentious path when dealing with the Linux kernel devs and the community as a whole.
It is pretty easy to tell that Matt is spinning a narrative in a “spitting off the cuff” manner instead of being methodical. Because he is spitting off the cuff, he does a very poor job of presenting and explaining the ideas, which leads to misinforming and misrepresenting the facts. To support his narrative he is using anecdotal evidence, instead of a well organized body of facts, which includes explaining contradictions. Matt conflates anti-cheat issues and Nvidia issues with Linux gaming as a whole, which amounts to yet another poor job on his part.
Overall the video is terrible at informing the audience and amounts to slinging mud and feces. The simple take aways are that Linux can be a relatively easy platform transition for many users. Some are stuck on Windows/Mac because of their hardware and/or software needs/desires. Some might never make a platform switch to Linux because they have no desire to do so, or are unwilling/unable to invest the time to make the switch. Before considering a platform switch to Linux, planning and preparation needs to happen, to avoid headache and frustration. Don’t switch cold turkey with zero prep work. Don’t take my word as the truth, take a look at the videos that I added to the original post.
I’m going to address some of the issues in the LinuxCast video below. NO one should follow your example, as it is a text book case in how to mislead and misinform. Matt’s face would be on such a text book.
X11 and OpenGL Backstory:
- X11 is 40 years old, release in June, 1984.
- X11 has been patched to death, suffers from extensive feature creep, yet is missing several modern features such as VRR and HDR support
- Wayland is the open source, open standard successor to X11
- OpenGL is 32 years old, release on 6/30/1992, and has been patched to death.
- Vulkan is the open source, open standard successor to OpenGL, and is vastly superior to OpenGL
- There is still OpenGL support and backward compatibility through Vulkan, but the compatibility component won’t last forever
- Wayland development started 16 years ago in 2008. Nvidia knew more than 5 years ago that Wayland would be the successor to X11 and support for X11 would come to an end.
- Nvidia knew about important Wayland release dates, yet still refused to work with the kernel devs, the Wayland devs, and the community as a whole to ensure a smooth transition for Nvidia users. This was deliberate on the part of Nvidia.
- the Wayland transition for AMD GPU and Intel GPU users has been relatively smooth because AMD and Intel work with the kernel devs, Wayland devs, and the community as a whole. There is rock solid kernel support for AMD and Intel hardware.
Nvidia developers tried to introduce driver software such that they (Nvidia) could take control of the Linux kernel and then use legal manuvering to attempt to take control of the entire Linux project. Nvidia is not our friend. See this article ==> https://www.phoronix.com/news/Linux-6.6-Illicit-NVIDIA-Change
Pay attention to the date of the article as it near (shortly before or after) the time of many major distro releases, where Wayland became the default surplanting X11. Some distros dropped X11 completely. Once one reads the Phoronix article is should be crystal clear that Nvidia is not our friend, and is intentionally causing issues that negatively affect their customers who chose to run Linux. This does NOT mean that one cannot use Nvidia GPUs with Wayland at all. The nuance involves performance issues, certain games crashing or not working, possible lack of feature parity between the Nvidia Linux driver and the Windows driver, and other issues.
Distros are making Wayland the default and/or dropping X11 completely because in order to get folks to move, we have to pull the plug of life support on the X11 dinosaur. No one in their right mind would want to run the Win 3.11 version of the Win API with a RTX 4000 series GPU. Win 3.11 is not a supported OS. So, attempting to continue support for X11 is like trying to keep Win 3.11 alive as a viable gaming platform in 2024. Again, Nvidia knew this years in advance. This is not a Linux cause problem, thus not a Linux pain point. This is a Nvidia problem and a Nvidia pain point. Nvidia does NOT care about their GPU customers. Most Nvidia GPU customers don’t know about this and don’t care to know about this. AMD GPU users don’t have to contend with Nvidia’s bad behavior. Matt says nothing about the above, but instead throws all the responsibility on to the Linux community. By shifting responsibility and blame onto the Linux community, Matt is absolving Nvidia of any wrong doing or responsibility. This is a massive misrepresentation of the facts.
Notice how long it took to explain all of this in writing.
Anti-cheat software:
Anti-cheat software and a lack of Linux support is unfortunate, but this is not a Linux problem. This is a deliberate choice of the devs/companies of certain games, to not allow their product to run on Linux. There is nothing the Linux kernel devs or community can do directly to change their decisions. Anyone who wants to play games, where the corporate owners disallow their product to run on Linux, are stuck playing it on Windows. The discussion around anti-cheat enabled games not running on Linux, completely ignores the cheating that occurred in Windows. Just because someone runs Linux does not automatically mean that they will cheat. However, those corporations don’t care. They’ve made their decision, which is final. To know which games run, run well, run poorly, or not at all, folks should just check protondb.com and removal all speculation. There are more than 1100 Steam games that run on Linux, which is a testament to the success of the Steam Deck.
Switching to Linux without preparation:
Matt speaks about how one could switch cold turkey, but it would most likely lead to lots of problems and the user ultimately going back to their previous platform. This isn’t unique to Linux. If one were on Windows and made a sudden jump to the Mac platform, there is a strong chance that the user would experience some pain and shock. What do you mean I can’t play Fornite on my $3000 M1 or M2 Mac? League of legends on Mac? Only if it is a x86 Mac. So while he describes this as a Linux pain point, it is not unique to Linux. Adobe didn’t release the Adobe Creative Suite for Windows until September 2003. If one tried to switch cold turkey from Mac to Windows in 2001, there was no Adobe suite available. Would we call that a Windows pain point? No. We would have said that was a poor user choice because they did not prepare for the platform switch. Again, not a Linux specific pain point and Matt does very poor job of explaining this.
Matt’s big 3 pain points and the rest that are supposedly ignored by the Linux community:
At about the 1 min mark, Matt starts describing the supposed big 3 (actually more than 3) Linux pain points. Some of which are not really pain points at all. Making a bootable USB key is not a pain point. If one can follow a simple set of instructions, a bootable USB key can be made. I’ve tested this on 70 year olds who are very much disinterested in “technology”. They don’t care to learn it, but they are able to follow simple instructions. Keep it simple and they can follow. The installation is rather simple for distros like Linux Mint and Pop_OS. This is especially true if one compares the installation process of Win 10, Linux Mint, and Pop_OS. The real issue is a large amount of Windows users have never gone through the Windows install process. They buy a new PC with Windows preloaded. I added some video links to the original post. In at least 2 of the videos, the installation process is shown. The videos are identified in the original post. With simple instructions, even 70 year olds can install Mint and Pop_OS. Disabling secure boot can be a pain point because the structure of UEFIs is not uniform so it can be difficult to provide guidance to an inexperienced end user. Lack of Adobe support is not a Linux pain point. Adobe refuses to bring their software to Linux. This is the same kind of strong resistance, from Adobe, to bringing their software to Windows, back in the late 1990s. Adobe’s corporate management has made a deliberate decision to not bring their software to Linux. Anyone depended on the Adobe ecosystem is basically stuck on Windows/Mac.
Streamer Hardware:
There is a lot of streamer hardware (stuff video game streamers use) that does not work on Linux. Again, this is not a Linux problem. The issue is the hardware manufacturers will not make drivers for Linux and won’t work with the community to help the community develop drivers for their hardware. This amounts to no Linux support. Folks like Raxx and Wudijo, would have to check if their streamer hardware has Linux support. If there is no support right now then they aren’t switching to Linux right now. Maybe the community might develop drivers, but it would be slow, time consuming process. Some stuff may never come to Linux.
I am annoyed about Microsoft making my good old PC redundant in a year’s time for sure. I can see that I bought it in the summer of 2014 so it will have seen more than ten years of good use by next year. Since 2014 I’ve had to replace a flat screen TV (it failed), I have been forced to replace a Samsung phone because it couldn’t run some vital apps, have also bought a new iPad also because the old OS didn’t support some apps anymore. I don’t buy the most expensive stuff in computers, phones and tablets but it’s still an investment every time.
