Flaky dumb blue jay lol

Read this before you switch to Linux.

- Problems about Linux you may want to know about from someone who used it for 10+ years.

There’s a lot of noise on the internet promoting Linux on the desktop, brought on by some idiotic decisions made by Microsoft and other tech companies, and it’s always brought on as this thing that will kill Windows and enshittification and AI slop and all that goodness.

However, as someone who’s been using desktop Linux in some shape or form since 2010, I’ve heard this story way too many times. Microsoft does something stupid, desktop Linux gets proselytised as the Windows killer, people legitimately wanting an escape try it then have problems, and then they sour on it and begrudgingly go back to Windows or buy a Mac while those that stay develop righteousness and both a superiority and a victim complex. I know this path, because it’s happened to me, my friends, and people I see online. While Windows’ userland sucks compared to KDE, which I’d love to use any day of the week, there’s stuff that Linux does worse than Windows especially with lower level stuff, which is important for adoption by developers, who can make things for average Joe users.

The reason I’ve made this post is so people who are wanting to switch to Linux for any reason have a realistic view of what they’re going up against.

Some ground rules:

  • These are based on experiences I’ve had, as well as things I commonly see on places like Bluesky.
  • The problems I’m stating here are not specific to one “distro”.
  • Real, substantial problems - not the odd tussle or inconsistency from something being unconditionally free.
  • I’ll state whether the problem can be solved, and if so, how.
  • The writing will be as non-technical as possible, however it’s not guaranteed.
  • It doesn’t matter if the problem isn’t to be blamed on Linux itself. They are still problems that prevent Linux desktop from progressing, so they’re still worth pointing out.

Missing software support

Anyone using the following are certainly gonna have a bad time, as there is no native and officially supported version available on Linux:

  • Adobe Creative Cloud
  • Affinity Suite
  • Apple Music
  • Clip Studio Paint
  • Microsoft Office
  • MusicBee
  • Paint Tool Sai
  • Anything for production and broadcasting using the Dante protocol or NDI Tools

The developers of some of these software, such as in the case of MusicBee, have publicly stated that Linux will not be supported at this time, or ever.

Yes, they can run in WINE, but it’s not a silver bullet. In some cases, updates can cause problems - MusicBee was broken on certain recent versions of WINE due to changes in how it handled memory. For an artist whose job relies on their software being reliable, I can’t blame them if this isn’t an option. Some bugs can last for years - I remember when I reported a bug on font redirection that affected MusicBee, and it didn’t get fixed until two years after. For people whose careers rely on this, this isn’t really an option.

People are very quick to prostelyse the alternatives even when applications like Adobe CC and Microsoft Office are industry standards. GIMP is a common suggestion as an alternative to image/photo editors, however it’s well known for its clunky UI. LibreOffice is recommended as a Microsoft Office alternative, however its ideological opposition to supporting MS Office files actively hurts it, as MS Office is the industry standard - for better or worse - and they aren’t meeting people where they’re at. OnlyOffice and its liberated fork Euro-Office are both solid options, at least.

I’ve tried alternatives to MusicBee that people have told me about, but they do not come close to MusicBee at all. A lot of Linux-native music players are way too basic, and the ones that are a bit more advanced are missing a lot of features. It’s to the point where a running joke I make is that the best music library player for Linux is Spotify. As someone on Bluesky said, MusicBee is one app that people stick to, and it’s to the point there are multiple threads on the MusicBee forums dedicated to getting MusicBee to run on Linux through WINE. In Apple Music’s case, Sidra is a nice drop-in for those who really don’t want to surrender to Spotify, however you do lose features present in the desktop versions that may be important to you, such as rule-based smart playlists, local music upload, and lossless audio. Whether you want to sacrifice these, I’m not the one to judge.

Another issue is when something is native to Linux, but has issues out of their control. For example, the video editor DaVinci Resolve does not support AAC audio, which is standard in MP4 files, due to patent encumberment. Some only support one distro, such as 3DCoat which only supports Ubuntu. I’ve heard plenty of stories about issues with virtual reality on Linux, even on the best supported headsets such as the Meta Quest (e.g. my friend’s controller gyro being mapped as the head on WiVRn for some reason).

Generally, if you’re curious about Linux you’ve got a lot of research to do, and one question you’ll need to ask is “what software will I lose by switching?” - otherwise you’re gonna have a pretty bad time.


Could this be solved? In the long run, yes!

Most essential software is cross-platform nowadays, however there are good apps for certain niches that have been popular, such as Krita for artists or JetBrains Rider for .NET/C# programming (of course, programming is one of Linux’s strongest suits). Some apps are designed specifically as stand-ins for their Windows equivalents, such as Fooyin for users of Foobar2000. It’s also not to say that WINE won’t get better, either. That MusicBee bug eventually got fixed. I actually think some of these issues could be fixed quicker if users knew where to report problems (although some community barriers will exist).

A good chunk of this lies in it being a chicken-and-egg issue: Linux isn’t supported because of the lack of software, however a lack of software leads to a lack of a real audience and therefore people not bothering to support Linux. There are signs that some tides are turning on this. Epic Games, who have historically been against porting Fortnite to Linux due to a lack of reliable anti-cheat methods, are now experimenting with a more reliable anti-cheat for Linux, with Fortnite as the first game to demonstrate it. No matter your opinion on Fortnite, this is a huge fucking deal. Xfer Records, an audio production software vendor known for the popular VST plugin Serum, have released a Linux native beta version of their VST for those willing to give it a test.

However, it’s not just a chicken-and-egg problem, as there are issues for developers that I’ll get to later, as well as issues from developers.

And to nip this in the bud: What about the “AI revolution”? In my opinion, this really depends on maintenance. Sidra is vibe-coded and AI agents mainly do the filling of the gaps to make Apple Music’s web client work properly as a standalone desktop app, however its maintainer has experience with other big projects like Ubuntu MATE, so I trust them. However the concern over vibe-coded apps by inexperienced people is real, to the point where the Linux app store Flathub initially banned all apps that were coded by AI in any form which does nothing other than reassure the OCD anxieties of the anti-AI movement. AI doesn’t really solve this beyond hastening; AI or not, you still need a competent human in the loop.

Missing / broken hardware support

If you use the following, you’re also going to have a bad time:

  • Certain drawing tablets
  • Certain fingerprint readers
  • Some cheap/no-name brand USB card readers you can get in shops or on Amazon
  • VR headsets that are not a Meta Quest
  • NVIDIA graphics cards that are not current-gen/RTX

Windows and even Mac to an extent are great for plug-and-play due to how well supported they are, but Windows is well engineered when it comes to this sort of thing due to how it’s built. If someone has to use the terminal to get something working or install some esoteric software to get it to work, that’s objectively not plug-and-play.

Like with software, niches are not fulfilled properly, without workarounds if it even works. My headset - the PlayStation VR 2 - technically works on Linux with a fork of WINE designed for SteamVR drivers, except no it doesn’t because the kernel has issues with Bluetooth polling rates that isn’t a thing on Windows. In the case of the card reader, the reader communicated via a different method that regular USB card readers don’t really communicate with, and the correct answer on getting it working was downvoted. It’s not out of the question that someone might buy a card reader from a supermarket or on Amazon expecting it to not have esoteric behaviour.

While NVIDIA support has been getting better, there have been issues with people being unable to run older cards that still work and wouldn’t be reasonable to throw away. NVIDIA has recently stopped support for 10xx GPUs, which I know are still being used to this day.

I also have an anecdote for this. My computer has Ethernet and Wi-Fi chips from Intel, however ASUS - the vendor of my motherboard - fucked up firmware code handling the power management, leading the drivers for both components to crash and leave my install in a bad state. You can blame ASUS or even me all you want, but most people are going to install Linux on their existing hardware, rather than buy an entirely new machine.

Hardware is something you’ll probably need to do more extensive research on, unless you buy hardware that is certified to run on Linux.


CTBS? Much like with software: Yes, although to a lesser extent in some cases.

Already there are projects tackling the hardware problem, such as the cross-platform OpenTabletDriver. Ignition, the WINE fork for SteamVR, is a step in the right direction. Due to what I stated earlier, hardware support is also a chicken-and-egg issue and a developer experience issue. Hell, Sony supports the DualSense (PS5 controller) really well on Linux. While not perfect (it messed up on DankPods’ testing), Bazzite does try its best to support NVIDIA GPUs.

Some of the responsibility also lies on the hardware vendors to fix their shit. ASUS seems to have fixed the bug that led to the crashing.

The horrendous state of desktop virtualisation

While technically a software issue, this warrants its own section because of how atrociously bad it is. As a primer, virtual machines are essentially “computers in a computer” that you can run an entire OS on. They’re big in the cloud industry but also has its uses in the desktop. It’s a sane assumption to make that people will want to virtualise other operating systems on Linux, to fill any gaps left out by native offerings or WINE bugs. However, virtualising Windows is simply a no-go right now due to the lack of GPU acceleration.

VMware at the moment is the best we’ve got for running Windows guests on Linux, as it has proper GPU-accelerated video (even if limited), however it’s not great either. Clipboard is broken on modern Linux desktops, requiring you to work around it in a convoluted way.

VirtualBox is unreliable no matter what OS runs on the bare metal - I’ve had issues with Windows VMs on Linux, as well as Linux VMs on Windows. Blame Oracle for this.

Then there’s the native solution - libvirt, QEMU, virt-manager, whatever you want to call it. There are no virtual GPU drivers at all for Windows with this setup, and it seems like some software made to make using the VM easier for desktop users is being deprecated by Red Hat, with VNC touted as the alternative. Red Hat is a cloud company, so I’m not surprised but nonetheless this is frustrating. The common solution is to basically attach an entire physical GPU to a virtual machine and then run experimental software to pipe the display to a window. This is basically a non-starter for me; I am never doing this just to use any operating system.

WinBoat seems the closest to a usable virtualised Windows experience right now, although I’d rather use anything other than a remote desktop protocol given I would need audio for the things I’m working and audio on WinBoat is not great for that reason.


CTBS? Yes, although when I am not sure on. I am aware of offerings for libvirt, and I know WinBoat is also working on this with LLM assistance.

Workaround after workaround

Linux users like to make fun of people trying to make a local user account on Windows using the Terminal or the registry editor. What they conveniently leave out is that this only happens once on an install, and for some the ends justifies the means. There’s a stark difference between “run this terminal command once once and you get a local account for life and can get back into what you were doing” and “oh, [insert app here] does just work on Linux! Just do this multi-step process in the terminal…” - something I actually touched on here.

The tl;dr: if it helps Gets Shit Done, and you only need to do it once or seldomly, then to the median user it’s worth it. This is why a lot of people still went through the terminal to unlock the three-year extended security update plan on Windows 10 for free. Staying on Windows 10 is worth more to these people than Linux and Windows 11 are since it gets them back into what they were doing instead of worrying over the operating system.

While desktop Linux has progressed and people who just need a web browser can join the power users on Linux, there are still some things the median user will do that need workarounds using the terminal or other non-conventional thing. It’s why I don’t bother with Windows virtual machines, or even VR on Linux.


CTBS? Yes, as software and hardware support improves, though Linux users need to stop evangelising the terminal as much as they do and shaming Windows users for using it once to Get Shit Done. A good GUI app will absolutely wipe the floor with a decent terminal/console program.

Memory management

Desktop Linux has more efficient desktops, which makes things a lot quicker and snappier to use compared to Windows, however its memory management? hahahahaha, no.

Windows and Mac both make pretty hefty use of swap, a portion of memory saved to the drive, and I’ve not had to deal with slowdowns or app instability as a result. On Linux, if the memory and swap get full it will just drunkenly shoot whatever app it can. I’ve ran into this way too many times when using virtual machines particularly.


CTBS? No reason not to, given that most of it is probably an issue with distros. Distros should make aggressive use of swap just like everyone else, and some already do. But some distros like CachyOS use “zram” instead which handles this in RAM and doesn’t give Linux much leeway for recovery. For the technical lot, you may wanna read this post by Chris Down.

Distro inconsistency and decision paralysis

“Works on my machine” is an ongoing joke in the Linux community, because of the vast amounts of inconsistent behaviour between people. Most of the blame has to go to the distros and the fragmentation this model has created. Ideally, there’d be just one Linux OS for users to use and developers to work with, but that isn’t the world we live in.

I’ve been running and writing this on CachyOS (basically dogfooding myself). Despite Fedora matching my release cycle preference the best, I used CachyOS because I knew everything would work. While I’ve been fine with CachyOS, I cannot say that for everyone. A friend of mine went back to Windows as CachyOS didn’t work with their game controllers, while it worked fine on Bazzite and SteamOS. You could ask why they didn’t just stick to either of those, however the issue here is they wanted a Linux distro that wasn’t as locked down (both are considered “immutable”, here meaning a change to the system files will be wiped after an update).

Another friend had an issue on an Arch-based distro, where playing TikTok videos on a web browser would cause Discord to have a memory leak. I tried to recreate this in any way possible, but could not. They’re now dual-booting with Windows 10.

People get shouted at not to use Ubuntu, even though it’s still one of the most well known Linux distro brands out there. The user cannot be blamed for putting trust in Ubuntu for this reason. What doesn’t help is that Ubuntu is one of the most commonly targeted distros for developers - it’s not a surprise to see apps only support Ubuntu, such as 3DCoat.

And as my own anecdote: I had an issue on Fedora where WINE wouldn’t play any audio. Normally this is because the 32-bit versions of the dependencies aren’t installed out of the box, but I did this and it still didn’t work.

Windows and Mac generally don’t change much at the lower level, meaning drivers and apps will work generally consistently. Since desktop Linux has different distributions of it, and some of them may not be the most consistent experience, you’re left thinking about not only whether a distro will have all the software you want, but whether it’ll even work or whether you’ll get shouted at for picking “the wrong distro”. It creates decision paralysis, which is even worse when you have neurodivergences/mental conditions that bolsters this such as ADHD.


CTBS? Short-term: with bug reporting, sure. Same goes for if people are fine with immutable distros. These sort of distros provide an “image” of a working system that people can deploy to their own PCs, with software being installed at the user level instead of a system level like a normal distro would.

Long-term, there needs to be some sort of standard for Linux distros to abide by, and there have been efforts to do this in fairness, such as the Open Gaming Collective. But given the fractured nature of desktop Linux, it’s a lot harder to get people co-operating.

Problems for developers

“Linux is great for developers!” is a common thing to hear. However, that’s only because it’s a joy to develop in and not to develop for. If you’ve had issues with certain apps or wondered why some apps only support Ubuntu or Red Hat Enterprise Linux, this is why.

Linux is a constantly growing and moving target, and it’s inconsistent at that. You’re not just looking at catering to different distros, you’re looking at different desktop environments that don’t implement everything you need. The biggest culprits are glibc (which handles the “core” for many apps), and Wayland (which is the current moving standard for the Linux desktop).

glibc has a habit of moving fast and breaking things, to the point that Linux’s creator had complained about it over a decade ago. Given that it’s the “core” for basically the desktop portion of Linux, it’s not great that it breaks too easily. Meanwhile, Wayland - which works using protocols for apps and desktop environments to communicate with each other - will try to block protocols for desktop paradigms that are normal everywhere else, like window positioning or surface suspension (so apps know when they’re minimised), due to an ideology that is just plainly wrong or is too extreme. If you use a UI toolkit, you may have had this abstracted for you and it’s not really a big problem, but if you write for such toolkits or otherwise do anything lower-level, good luck. The developers of Avalonia, a UI kit for .NET, wrote a great post about this.

Another joke in the Linux community is that “Win32 is the most/only stable ABI for Linux”. If you’re not technical, it basically means to make a good, stable experience with your app on Linux you need to write it for Windows first, and this has happened in practice: a lot of game developers and to an extent software developers outside of the gaming industry have resorted to letting Valve and WINE handle it.

For a good, strongly-worded, and angry read-up on this, PJB has a great post noting all the problems they had with Linux and goes into more detail with the glibc and Wayland problems. JangaFX’s post on the atrocious state of Linux backwards compatibility is also a good read.


CTBS? This one is tricky, and right now I lean towards “no” in the long term. While UI toolkits can abstract a lot of the issues for most people, anyone needing to write lower level will struggle regardless, and this is why developers of larger, more complex software like games don’t bother and delegate the running of their app to WINE instead. Without gutting glibc I can’t see a meaningful change, and people get tribalistic about this sort of thing, especially when you suggest ripping out something by the GNU project.

Long-term, a pragmatic push towards development would be best, but developers with egos would need to be pushed one way or another. Valve got surface suspension fixed on Wayland by updating Vulkan, the graphics spec, to make Wayland’s behaviour “illegal” in the spec. Valve should not have needed to do this in the first place. Wayland needs to treat the things they don’t like as features if they exist in a working state on Windows and Mac, for example. Multi-window apps are still a thing, and it’s a well known standard in some industries - thankfully they budged on this, but again - they shouldn’t have to need to be budged on this. Linus’ “it’s not a bug, it’s a feature” mantra when it comes to not breaking the userspace (the part/s of the OS the user will be using) is very much needed here.

Something must change, otherwise Linux is going to be a massive pain to develop for. I also don’t blame developers for letting AI handle it, either - as I said before AI exemplifies a maintenance concern, but I can see how enticing it is to let the computer deal with the problems the humans made.

The community

Like any operating system, you’ll have problems you’ll want to fix them. There are some great souls in the Linux community who are helpful at best and clumsy at worst, however for every great soul there seems to be like three bad apples willing to make you question why you bothered installing Linux in the first place.

The Linux community - and broadly speaking, the FOSS community - tends to lean on ideological extremism and at times purity, which I am not a fan of for mental health reasons. There tends to be a focus on privacy and sticking it to Big Tech, and while these are noble principles I think anyone with a functioning mind can get behind, the way it is approached by these communities is clumsy at best and extremely toxic at worst. Tribalism and attempts of purity is common in these circles, and in the case of Linux it gets to the point where things regular users don’t give a shit about like service systems end up being the topic of flamewars.

The things I’ve seen dealing with bad apples in the Linux community are as follows:

  • a focus on ideology over actually making something good.
  • a lack of introspection/looking inwards
  • desire to control other people’s experiences with the OS.
  • entitlement not just towards developers but users of the operating system and telling them what they should and shouldn’t want.
  • treating ideology and software as an extension of themselves, like a religion - any critique of Linux/FOSS is treated as a critique of them personally.

While other OSes and even other software have this, it’s most intense in Linux and the FOSS community, from what I’ve seen. These groups have been compared in a derogatory tone to militant vegans, and I do not blame people for doing that.

I also find that the anti-Big Tech ideology keeps people complacent. The fact that Windows has gotten worse towards the median person, while desktop Linux has stagnated is not a good sign for Linux. It means that Windows has basically stooped to Linux’s level, rather than Linux getting better. In other words, it’s created the complacency for crap.

This unfortunately extends to the developers on this platform, to an extent, and why I consider it a problem worthy enough to write here. The privacy ideology has led to Wayland making some extremely stupid decisions like the surface suspension one I said earlier. GNOME developers are known for their ego, and the drama that ensues - they have their vision of what they want to be, but won’t budge for software that verges differently and is a good part of why Wayland has been frustrating for developers.

The generative AI boom and specifically the rise of LLMs has intensified this problem. KDE got into drama over trying to stop LLM-generated slop, something I ranted about given the behaviour I saw. (it’s worth noting that I am highly critical of the anti-AI movement due to this behaviour.)


CTBS? Unfortunately, no - at least, not as long as the ideologues control the community and thus the trajectory of the Linux desktop. As I said, the generative AI boom has made this problem worse, and it is only going to intensify as more software - including on the Linux desktop - use LLMs.

This is by far the most frustrating part. A lot of problems with desktop Linux would be fixed if the community broadly didn’t act the way they did, including the developers. A bit of wiggle room for quote-on-quote “sinners” is required for Linux to be adopted. The Linux kernel could make swathes of progress tomorrow, while the community is still bickering over shit that doesn’t matter.

ADHD and OCD/perfectionism overthinking

This one is very personal to me. It’s also not to say everyone with ADHD and/or OCD are going to deal with this. However, as I’ve gotten diagnosed and treated, and I learned more about myself, I’ve found out that there are parts of Linux that constantly triggered perfectionist tendencies and I want to warn people on this.

I’ve already touched on decision paralysis beforehand, but in ADHD brains this is intensified to the point every decision feels like life or death. The ADDA has a great write-up on how this sort of thing affects ADHD brains. However, if you suffer from OCD focused on perfectionism, Linux is going to fire that very intensely (especially if you have ADHD) and I’d suggest you stay on the OS you’re using right now until you know what you deeply, and truly, want from your computer.

The mantra I’ll give is “the best operating system is the one you’re using right now” - it’s easier to work around the perfectionism and paralysis simply by staying on the thing you’re already on.


CTBS? Well, this is something you - and I - have to deal with, however we can. Medication, therapy, and self-help will help get you there.

Some of the stuff I suggested before, such as lessening the amount of distros, would help tho. Having desktop Linux set around a set of standards per feature, like with systemd, basically eliminates this while making desktop Linux better for everyone.

Conclusion

So, should you use Linux?

i dunno lol.

That’s up to you. If these don’t sound like barriers, then go ahead! Hell, I am optimistic for a lot of these problems being fixed, as you can see! There’s not a lot we can do about the worse technology desktop Linux is built on top, but that’s whatever. The biggest barrier for me right now is the community, as it hinders progress which would eventually fix these issues much quicker. And they probably won’t like this post that much. Ah well. It’s something they need to read. Seeing YouTubers and generally people online constantly evangelise an OS which has flaws making it potentially unusable to people did not sit well with me, especially having used it for a decade or so.

(also, yes I did a post like this in the past when I was on WordPress. This is essentially a remake of that post.)


Tags: Linux, Operating Systems Previous:
Porter Robinson - Mirror
Next: You're already at the end!