Executing the Linux jump command
Executing the Linux jump command
I strongly backed Intel and Nvidia for a long time. AMD comes with driver and USB challenges, but the benefits of choosing AMD greatly surpass the drawbacks. I've been using Hot Box with a 5800x and 6800xt since December. So far, I haven't encountered any USB or graphics driver problems. I'm planning to explore DXVK and Wayland. That part of your answer was really confusing for me. Usually I just install software and don't care about the details, which is why I'm moving to Linux. I enjoy learning. I know NVIDIA dominates the market and will keep doing so with some specialized tools. But a key reason I switched from NVIDIA GPUs for everyday use was my 2070. I used it for a couple of months after its release until the 6800 xt arrived. I never used any of their streaming apps, RTX or DLSS. I belong to the group that prefers rasterization speed. For me, NVIDIA feels more like Windows—powerful but complex to manage. They have the biggest market share, but sometimes it feels like they add unnecessary complexity. I'm also wondering about your reasoning for building all AMD components. Do you think an AMD CPU and GPU could improve cross-platform compatibility and game performance in the future? In my view, developers will focus more on optimizing for RDNA 2 and 8c/16t CPUs in upcoming consoles, which could mean PCs get more development time and run better. FSR seems simpler to implement compared to other options. To be clear, I'm not saying AMD is always better than Intel or Nvidia in every situation. If a studio invests time in Nvidia, it can still perform well with RTX and DLSS/FSR. My take on Linux aligns with this idea. W10 appears to be getting more tightly controlled, and W11 seems even stricter.
It's okay to feel a bit confused if you try to master everything about Linux right away. Begin using it, and the specifics will become clearer over time (this is exactly how I learned Linux and programming with Python). KDE offers a high level of personalization. It resembles Windows by default, but you can quickly adapt it to look like MacOS or another system. On the other hand, the GNOME team aims for sensible defaults from their perspective and tends to discourage extensive theming. That's the aspect I find most limiting (besides the fact that it feels like a touch interface on a touchless screen). Choose what suits you. Regarding hardware choices, if you decide to go Linux, avoid AMD because Nvidia hasn't released open-source drivers for their chips (at least while Jensen Huang is in charge). Plus, AMD drivers come bundled with the kernel, so you won't need to search for them after installation—this gives a smoother setup experience compared to Windows. And the fact that Steam Deck runs on RDNA2 will definitely boost its performance in the future.
Just because a console runs on AMD with specific optimizations doesn't guarantee compatibility or identical performance gains on a PC. Consoles usually remove features and add console-specific tools, along with different APIs. Even within the console market we’re focusing on, two distinct platforms can exist despite similar specs. As long as NVIDIA maintains its dominance, most ports will likely continue to prioritize it. This trend is reinforced by NVIDIA’s tendency to actively support major game development. AMD seldom takes such a proactive role. When it comes to CPUs, success largely depends on market share and whether the optimization is tailored for a particular processor. Many titles rely on a standard compatible version. Of course, this isn’t confirmed. The main issue is that NVIDIA often pushes for solutions closely tied to its hardware. If you’re frustrated by Windows restrictions, you might prefer Gnome instead. The goal of Gnome is simplicity, keeping most functionality behind a registry. Sounds familiar? Yes, Gnome has extensions that are often seen as afterthoughts, with the team debating their future. The community will always adapt, sometimes by creating forks or alternative distributions. Theme support isn’t a real feature—Gnome is built around one style sheet, and changes are usually treated as workarounds. Gnome 3/40 was never meant to offer flexibility; it was built for workstations and designed to be difficult to modify. Microsoft follows a similar approach, though less restrictive. Personally, I have mixed feelings about Gnome. I appreciate its ease for single-monitor setups, where it performs best, but for other tasks I switch to KDE. If you want a glimpse of Gnome’s intended design, try booting a Fedora Workstation live environment.
User @patemathic provided a clear comparison. Discord spyware functions well on Linux, whereas Spotify spyware shows mixed results—functioned once but seemed unstable or incomplete unless paid. You tend to avoid spyware for software lacking GPL or MIT licenses, since it's hard to verify if it's malicious without source access. This approach aligns with privacy-conscious GNU+Linux users who prioritize transparency. Some games, like CS:GO, work smoothly on Steam platforms without additional tools. You can explore compatibility lists at protondb.com and check gaming forums for troubleshooting tips. Be cautious—many anti-cheat systems depend on Windows-specific spyware, making them difficult to bypass without deep technical expertise. Experience varies between Debian, Ubuntu, Manjaro, and Arch Linux, with Manjaro offering frequent updates but also potential stability issues.
Spotify remains fully functional with no significant changes over the past couple of years. A lot of GPL-licensed programs are disguised as spyware. Most users aren’t concerned about accessing the source code. Few can even grasp much of it, and for others we rarely examine every line of code for each installed program. Linux contains a lot of proprietary components—without them, your system would likely be unusable. Take linux-firmware as an example of its most basic requirements. I’ve encountered network routers that are more deceptive than typical Windows spyware, and other devices commonly found on networks.
@Nayr438 " Spotify still works fine and nothing about it has changed in the past year or two." Hmmm I do not know, perhaps it was a distribution issue.. :/ I cannot correctly recall what the problem was, but I think it was that I could not open the settings or search for songs.. I forgot. "1. There is plenty of GPL licensed software that is spyware." "plenty" - sure, mostly those that were originally Windows and/or MacOS only. I cannot deny that stuff such as telemetry cannot be added, even if it's seen, one example is the Audacity project, which has recently been bought by some company who's name I forgot, and they changed their privacy policy basically going against the GPL license that it has(or had). And many distributions seem to have either stop updating it or just forked the source code before it was telemetry-zed or just remove the telemetry and keep all the features that might or might not be added by that company. "2. Most people don't care if they can read the source code. Most people can't even begin to understand a lot of it, and for the rest we are not reading every piece of code for every piece of software we install." Of course not, I didn't even think so. Although it's not just about reading the code, most people don't have to understand it. Please watch some of TEDx talks that Richard Stallman made, they are on YouTube.. I believe links to other websites are disallowed here. But imagine it like this: imagine someone murdering people and they knowingly let you see them - there is a chance that you'll keep quiet, perhaps out of fear. But perhaps there's a chance you'll catch the bad guy and report it to someone.. Same idea can be applied here - if someone, even one programmer finds telemetry/spyware and malware code in some software - chances are that they will talk about it on some forums, maybe tell their friends, and perhaps even make blogs and videos about it - like I said - Audacity is a big example here, as someone discovered their policies and their intentions of putting telemetry, so, thanks to this, it was spread by people and now myself and yourself included know about it. If we do not believe it - we can simply just check the source code itself. We do not have to be developers - someone can make a video/text explaining what each line of code does and if the majority of other programmers disagree and comment "that's not true" - that'd be a red warning. Also when it comes to stuff like malware - you could just replicate the code in your own program, programming is not difficult to learn, and take this from a retard, myself, which learns some stuff slowly. "3. Linux is full of non open-source code, you probably wouldn't be able to use your system in any useful way without it. Just look at linux-firmware for it's most basic inclusion." I got 3 arguments against this: 1. Software CAN be reverse-engineered, but it's so difficult that in most cases it is not being done, but in important parts such as in the kernel - I believe they might have done just that, and if not - well, there's 2 other arguments: 2. Just use a 100% GPL freedom software distribution such as Parabola, and others, listed on the GNU website, if your hardware is compatible with it. 3. "Linux is full of non open-source code" - full? Not really. Sure, there might be some blobs aka little parts that's might contain some non-free source code in it, but that's mainly because some hardware companies do not want to share their code with the Linux developers, so it's not Linux's fault really. And even so - Linux is so much better when it comes to being spyware/malware-free that it's the best thing around, Windows 10/11 and MacOS are exponentially worse so yeah. "4. I have seen network routers that are more malicious than your average Windows Spyware, not to mention other devices usually on a network." So? Protect yourself, harden you OS, use firewalls, fail2ban, etc. Or just you know.. lol.. get a better network router. You got anything else to embarrass yourself with? :'D
Spent the first day without any problems. I'm using Pop OS with their standard Cosmic/Gnome setup. I'll wait a few days to see if I like the look. @Nayr438 had a point—Gnome seems too restrictive for my needs. I did notice some performance drops when trying to use the terminal, but it's mostly minor. Adjusting to it will take time. Plus, there are plenty of other Linux options that make things easier. So far, no major regrets.