Tried Windows 11 after years on Linux and changed his mind

Here's an article I related to, to a certain extent, which is the one you're reading on screen. Before I begin, a quick clarification: this isn't a criticism of Linux.

We use Linux practically every day. For example:

• Android has Linux behind it.
• Steam Deck has Linux behind it.
• Surely, if you have a smart refrigerator, it's also going to have Linux.
• Among many other gadgets.

In other words, Linux is everywhere. The only thing is that, as a "work operating system," it's sometimes not used as much. Just look at any survey to see who has the largest market share.

My personal experience

I'd like to clarify that it's not necessarily due to a lack of skills. I've been programming for over 15 years, I love programming, and I worked with Linux for a good part of my life (especially in college). However, I didn't continue using it much after that, for reasons very similar to those mentioned by the author of the article.

In my particular case, the main reason is simple: I just don't have enough time. I have too many things to do, and even if it hurts someone, I don't want to spend time messing around with Linux. Yes, in the end, it's knowledge that remains, but when you're working, you learn a lot more programming (which is what I'm truly passionate about) than configuring an operating system.

I enjoy programming more than fighting with system configurations. In fact, here you can see all the projects I manage daily in Visual Studio Code. That's the reason why I don't use Linux as my primary work system.

Let me clarify again: I'm not saying this to argue with anyone. I'm simply reading an article that I resonated with.

Distributions and the “manual problem”

When I worked with Linux, I liked a lot of distributions. I tried Fedora, Ubuntu, and also Linux Mint. All very good, but for me the problem is that they're too manual.

Almost everything has to be configured yourself. And of course, if you prefer to spend your time doing other things (like programming, in my case), you choose more user-friendly operating systems. It's that simple.

This person also shares their experience: they were a Linux expert for 8 years, completely abandoned other operating systems, and when they tried Windows, they decided not to go back to Linux.

In short, they found Windows more practical and efficient for their daily work. And I completely understand.

Linux vs. Windows: Total Control vs. Practicality

Linux is for those who want total control: tinkering, customizing everything, and tweaking every last detail. Windows, on the other hand, is more closed, but also more direct and simple.

When I tried it back in the day, I was fascinated by the ability to change themes, install packages, and tweak everything. But there comes a point in life where that's no longer a priority. You want to spend your time working, not configuring.

The support problem

Another major flaw, though not directly Linux's fault, is the lack of support from some companies. For example, Nvidia barely offers support on Linux.

The author of the article mentions that he always had issues with the graphical interface and, moreover, with games. In my case, I completely understand. Yes, I know that with Steam Deck and some distributions, games run well, even with higher FPS than on Windows. But, speaking of general-purpose computers, the reality is that Windows is still more reliable in that area.

My experience with Windows

I almost never have configuration issues on Windows. Once the drivers are installed, everything works fine. Sure, some bugs may appear, but just reboot and that's it.

On Linux, on the other hand, I ended up spending more time troubleshooting than actually working. And that's the key point: I prefer to spend my time programming, not configuring.

Not everything is black or white

I'm not saying that Linux is unusable. Everything has its audience.

In my case, I use Windows as a general-purpose system. But when I want something more convenient for programming, I turn to Mac. For example: Python works terribly on Windows. On Mac or Linux, it works much better.

In fact, in this online store project with Django and Tailwind, on Windows I always run into errors with virtual environments. As soon as I open the terminal, it doesn't even recognize the venv, which doesn't happen on Linux or Mac.

Windows, Linux, and Mac each have their own space. In my case:

• I use Windows as a general-purpose machine.
• I use Mac for programming and taking advantage of the Apple ecosystem.
• I respect Linux a lot, but it's not my choice for work these days.
• I prefer to spend my time working, not fiddling with settings.

Why don't I use Linux and use Windows and MacOS instead?

Here, I want to quickly give you my opinion, or rather, the reason why I don't use Linux. More than just an opinion, it's a choice based on my experience and needs.

Using Multiple Systems

I already use two operating systems: Windows and Mac. I've always been one of those who enjoys trying a little bit of everything, mixing tools, and getting the most out of each system. As I mentioned in another video, I use several computers and systems, so adding a third like Linux is starting to feel unnecessary.

My Experience with Linux

Yes, at some point I used Linux. This was in college, practically imposed on me. When I got to the second subject of my degree, which was Data Structures, we were forced to install Linux no matter what. At that time, I installed it on a laptop I had at the time (which I recently sold). I used Instalibuto, and it was my first real contact with the system.

That first experience, like that of many, was somewhat rough. Everything felt more basic, more manual, compared to Windows, which is the most widely used operating system. And if you're moving from Mac to Linux, that feeling of rusticity is even more pronounced.

Why don't I use it professionally?

I used Linux in that academic context because it was necessary for some specific configurations and tools. However, I don't see it as necessary in a professional setting. On the one hand, everything is much more manual. Let me give you an example: I work a lot with PHP and Laravel. On Windows and Mac, we already have tools like Laravel or Laravel Hardware, which practically install themselves. On the other hand, on Linux, everything is manual: installing Apache, PHP, MySQL, configuring them one by one... instead of simply running an .exe and that's it.

We live in an age where everything must be fast and functional. I don't want to waste time on basic configurations that are already resolved on other systems.

Many versions and flavors

Another important reason is the lack of stability between versions. Yes, you can run five commands to install what you need, but when versions change, so do the packages and commands. Sometimes the scripts that worked before stop working. If you get an error on top of that, you have to search with less documentation available, and you end up spending more time getting the same thing you already have with Windows or Mac.

I tried several distributions.

I tried distributions like Fedora and Linux Mint, and I liked them quite a bit. But I ended up abandoning them for the same reasons. Although I always like to offer options (which is why I have courses and books with the same adapted content), I don't offer support for Linux because I no longer use it.

It's also complicated to create content for each distribution: one asks you how it works in Fedora, another in Arch, another in Debian... and on top of that, they change with each new version. For me, that's just a waste of time if I'm not going to work in that environment.

Why Windows and Mac?

With Windows, although it's sometimes a bit more messy and causes errors, it's the most comprehensive system. I affectionately call it "the fifth" because it sometimes crashes. But there's virtually no software that doesn't have a Windows version. If it doesn't, it's a rare occurrence. In 95% of cases, you'll find what you need.

And with Mac, my choice is more about the iOS ecosystem. As a developer, I'm interested in publishing for iOS. I haven't released my academic app on iOS yet, but it's something I'd like to do at some point. I haven't yet because I want to polish it further and because you have to pay $100 a year, which annoys me a bit, but I know I'll publish it eventually. If I used Linux instead of Mac, I'd lose all access to that ecosystem.

In short

• Everything on Linux is more manual.
• I already have two systems that cover all my needs: Windows and Mac.
• I don't want to spend time configuring environments I don't use professionally.
• I want to maintain speed and efficiency in my work.
• And as a content creator, it makes no sense to offer support for a system I don't even use.

Linux is NOT for Everyone: When You Should Stay on Windows or macOS

The idea that "Linux is not for everyone" is a recurring debate in web development and technology. Although Linux has evolved in leaps and bounds, there are specific scenarios where staying on Windows or macOS remains the most practical option. Below, we will analyze the myths and realities about the learning curve, gaming performance, and software compatibility.

1. Understanding the Ecosystem: The Kernel and Distributions

It is essential to remember that Linux is not an operating system in itself, but the kernel. From this core, various organizations and communities build distributions (distros) that include the graphical interface, package management, and system optimization.

Unlike the generic nature of Windows, in Linux it is possible to choose a distribution tailored to specific needs:

• Immutable and High-Security Systems: Distributions like Bazzite offer a base system protected against direct modifications, managing software through isolated containers.
• Performance for Gaming and Development: Distributions like CachyOS incorporate highly optimized kernels for resource management in games and compilation environments.
• Modest Specification Computers: Lightweight options exist designed to maximize the lifespan of older hardware.

2. Software Compatibility: The True Reason to Stay on Windows or macOS

The main argument for not migrating to Linux does not lie in the complexity of use, but in the dependency on exclusive software. If your daily workflow requires specific tools from the Adobe suite or closed corporate ecosystems that lack native support or stable compatibility layers, staying on Windows or macOS is the ideal decision.

However, most workflows oriented toward web development, content creation with multiplatform applications (like DaVinci Resolve or OBS Studio), and the use of cloud suites operate with total normality and superior performance in Linux environments.

3. The Myth of the Terminal and Software Repositories

Historically, the need to interact with the command line pushed the average user away. Today, the use of the terminal is completely optional thanks to graphical software stores and visual managers like Octopi.

Furthermore, installing applications through centralized repositories offers substantial advantages in security and maintenance compared to manually downloading executables executable by executable on other operating systems.

4. Current State of Gaming on Linux: The Proton Revolution

The video game landscape on Linux changed radically following the arrival of tools like Proton developed by Valve. This translation layer allows running titles originally compiled for Windows with native performance in Linux environments.

The only persistent limitation in this area is concentrated in competitive video games that require kernel-level anti-cheat systems incompatible with Linux, or in advanced virtual reality (VR) configurations that require proprietary driver layers.

5. The Learning Curve and the Time Factor

Changing operating systems implies investing time in adapting to a new workflow. In the event of any configuration error, it is currently possible to rely on artificial intelligence assistants to diagnose the exact cause in a matter of minutes, eliminating the need to perform complex searches in forums.

Dividing problems into simple parts and choosing the right distribution from the start guarantees a smooth and efficient transition to the Linux environment.

This is a great time to switch to Linux

I consider this an excellent time to evaluate migrating from Windows to Linux. While transitioning from macOS can be more complex due to the tight integration of Apple's ecosystem (especially for developers focused on their platforms), Windows has become the most easily replaceable operating system. In recent years, Microsoft has increased the presence of background processes and telemetry, focusing on the forced integration of its proprietary artificial intelligence tools. This directly impacts system performance and creates the feeling of losing control over your own operating system.

Overcoming Proprietary Software Barriers

Historically, one of the main obstacles to making the permanent move to Linux has been reliance on proprietary software exclusive to Windows or macOS. In my content creation workflow, the primary bottleneck was Camtasia, the tool I used for screen recording. However, solid and professional alternatives exist on Linux:

• OBS Studio: An excellent open-source solution used for video capture and recording.
• DaVinci Resolve: One of the most advanced video editing, color correction, and post-production suites on the market.

Permission Systems in Linux and Finding Solutions

Despite the general stability of Linux, users may encounter technical challenges, particularly related to the file permission system and directory structure. In Windows, troubleshooting is often limited to reinstalling the application; in Linux, execution errors when launching a program are frequently due to improper permissions or missing required folders in the user path.

When attempting to run a program like DaVinci Resolve directly from the system launcher, the application may fail to open and provide no error information. In these cases, best practice is to launch the executable directly from the terminal to analyze the output logs and trace the root cause of the issue.

Using AI Assistants as Debugging Tools

The use of language models and artificial intelligence has established itself as a fundamental ally in technical support and system administration. However, it is important to distinguish the capabilities and limitations of each workspace environment:

Isolated Environment Models (Web Console Chatbots)

Tools like Gemini or ChatGPT are great for conceptual queries and general recommendations. However, because they operate in an environment completely isolated from your local machine, they cannot inspect the real state of the operating system, directory hierarchy, or user permissions. This can cause the model to hallucinate or suggest generic commands (such as recursively assigning permissions like chmod 777 or 755) that do not necessarily resolve the underlying conflict.

Tools with Local Terminal Access (OpenCode / CLI Agents)

For local system errors, using open CLI tools or agents (such as OpenCode or clients with runtime environment access) is significantly more efficient. Having permission to inspect the machine allows the tool to use system tracing utilities (like strace) to identify exactly which folders or files the application is trying to create and where reading or writing fails.

Generating Documentation and Continuous Learning

Offloading technical debugging to an automated tool does not mean disengaging from the process. Once the permission and folder structure issue is resolved, best practice is to ask the assistant for a detailed summary of the actions executed:

1. Error Identification: Understand exactly which folder or permission was blocking the application.
2. Applied Solution: Record the exact instructions and commands used to fix the failure.
3. Automation: Save the instructions in a Shell script file (.sh) to fix the issue immediately if it occurs again after a system update.

Complete Solution — DaVinci Resolve "Failed to create application support directories"

Diagnosis

DaVinci Resolve on Linux requires these directories to exist under /opt/resolve/ with write permissions for your user, but the installer does not automatically create them in all versions:

Directory Purpose

/opt/resolve/Extras DDM package downloads

/opt/resolve/Fairlight Fairlight audio data

/opt/resolve/Immersive Immersive content (Apple Immersive, etc.)

Full repair command

Copy and paste into your terminal:

# Create missing directories

sudo mkdir -p /opt/resolve/Extras /opt/resolve/Fairlight /opt/resolve/Immersive

 

# Grant read/write permissions to your user

sudo chmod 777 /opt/resolve/Extras /opt/resolve/Fairlight /opt/resolve/Immersive

sudo chown andres:andres /opt/resolve/Extras /opt/resolve/Fairlight /opt/resolve/Immersive

Launch Resolve

/opt/resolve/bin/resolve

Create quick access shortcut (optional)

If you want a shortcut in the KDE menu:

# Copy the desktop file

cp /opt/resolve/share/DaVinciResolve.desktop ~/.local/share/applications/

 

# Edit the Exec field if necessary

sed -i 's|Exec=.*|Exec=/opt/resolve/bin/resolve %f|' ~/.local/share/applications/DaVinciResolve.desktop

Diagnostic logs

If it fails again, check these files:

# Main Resolve log

cat ~/.local/share/DaVinciResolve/logs/ResolveDebug.txt | tail -30

 

# DDM (downloads) log

cat ~/.local/share/DaVinciResolve/logs/ddm.log | tail -10

Errors to look for:

- errno 13 = Permission Denied (missing permissions)

- Failed to create storage dir = Missing directory creation

- mkdir failed for directory = Specific missing directory

In conclusion, relying on AI assistants dramatically reduces the learning curve when migrating to Linux, transforming tedious technical issues into documented and automated learning opportunities.