I’ve used Linux for 30 years – 4 frustrations remain, including 2 that may push me to MacOS


Pop!_OS

Jack Wallen/ZDNET

Follow ZDNET: Add us as a preferred source on Google.


ZDNET’s key takeaways

  • Linux has been my default OS for decades.
  • Although it’s been an amazing journey, it’s not always perfect.
  • Here are a few gripes I still have about the open-source OS.

Since 1997, my experience with Linux has been nearly all positive. It’s very rare for me to run into an issue, and when I do, it’s usually easy to resolve. I’ve used Linux for desktops, laptops, tablets, phones, servers, and just about everything you can imagine. 

But that doesn’t mean everything has been perfect. Linux has a few lingering issues. In some cases, those issues have improved but have yet to be fully resolved. 

Also: After 30 years with Linux, I gave Windows 11 a chance – and found 9 clear problems

Two of the issues below have caused me recurring problems over the years; I even once had to say goodbye to one of my favorite distributions, Bodhi Linux, because of sound issues. One issue is merely a matter of taste (but it really bothers me).

Enough with the setup; let’s get to the issues.

1. Audio recording can be glitchy

This is probably the issue that has plagued me more than any other. Given that I work with a lot of audio and video, I’ve had to struggle with sound issues on Linux for years. Now, I’m not talking about average sound usage here. Nearly all Linux distributions are straight-up plug-and-play when you want to listen to your favorite tunes on Spotify.

It’s when you dive into the world of recording sound that things can get frustrating. From stuttering, dropping out, or simply not playing, sound can be problematic. Years ago, I had a side gig as an audiobook narrator, and Audacity on Linux gave me fits trying to get it to work with any regularity. I would have to restart the system and jump through all sorts of hoops.

Also: I’m a creator and my new favorite Linux distro is multimedia perfection – here’s why

Fast forward to last year, when I went to record another audiobook, and the same problem hit me. Fortunately, this time I was able to easily solve the problem by plugging my mic into a Focusrite Scarlet 2i2, and all was well. 

Most people don’t have an external sound interface lying around, so this issue needs to be addressed. Keep in mind that sound issues don’t plague only Linux; Linux seems to suffer from them more than other platforms. This issue isn’t a Linux kernel problem per se, but rather an issue with underlying sound servers such as Pipewire. (Pipewire is the replacement for ALSA, which had serious issues that seemed to never be resolved.) 

These issues are not as bad now as they once were, but you can bet that if I have to record, edit, or mix sound, I’ll probably do it on MacOS, because I don’t always have time to troubleshoot.

2. Laptops don’t suspend properly

If you use Linux on a laptop, you probably know that suspend/resume can be a problem. You close the lid, and when you open it, it’s always a guess whether it’ll come back to life or the battery is dead. 

Also: The best Linux laptops: Expert tested for students, hobbyists, and pros

This is not the case with every distribution, and it can also be a release-to-release issue. I’ve experienced one distro release where suspension worked, and then in the next release, it wouldn’t. This is the main reason I tend to go for my MacBook, rather than one of my Linux-based laptops. Battery life on the Linux machines is fine unless I close the lid, at which point all bets are off due to suspend issues. Or, I might open a lid of one of my Linux laptops and the OS won’t come out of suspension. 

In some instances, the problem goes to video driver issues that prevent the OS from waking up. As well, it can vary from hardware to hardware, so Linux and hibernation can be a real crap shoot.

3. Bluetooth disconnects

Bluetooth problems aren’t isolated to Linux. I’ve experienced Bluetooth issues on Linux, MacOS, Windows, and Android. The difference is that there have been times when the solution on Linux was to simply not use Bluetooth.

And that’s not always an option.

Also: Frustrated with your Bluetooth? How multipoint works – and why it sometimes won’t

This Bluetooth issue is most often related to sound, although it can depend on the hardware you’re using. For example, I use three different sound amps, and I can only connect one of them — the WiiM Amp Ultra — via Bluetooth with any regularity. The other amps show up, and I can connect to them, but Bluetooth immediately disconnects.

The Bluetooth issue isn’t isolated to sound devices; it also affects mice and keyboards. I have two mice: one Microsoft Bluetooth and one Logitech that uses a wireless receiver. The Logitech never has problems, but the Microsoft Bluetooth mouse often does.

If you do need to use Bluetooth on Linux, I would recommend installing the Blueman Bluetooth manager, as it gives you more control and troubleshooting options.

4. Default dark themes

This is a matter of personal preference, but it only ever comes up on Linux. For whatever reason, developers have decided that dark themes are the best option. When I install a Linux distribution, there’s about a 99.9% chance that the distro will default to a dark theme.

Also: The most beautiful Linux distributions 

I get the idea behind dark themes: they are easier on the eyes in low-light conditions. But who works most of the day in darkness? 

Not me. The very first thing I always do with a new Linux installation is switch it to a light theme. I may be the odd one out, but dark themes hurt my eyes.

It would be nice if developers followed the lead of distributions that give users a choice on first login about which theme to use. This is especially true for new Linux users who might not know exactly where to change the theme at first.

That’s it for my list of gripes. It’s short and sweet, but it would certainly be nice if these issues were addressed once and for all.





Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Another day, another politically motivated attack in the United States.

This morning’s shooting at a Dallas ICE detention facility – where a sniper killed two detainees and wounded another before taking his own life prompted me to revisit a question that’s been troubling me: Is political violence actually increasing in America, or does it just feel that way?

To explore this, I’ve conducted what I’ll call a methodological experiment.

Rather than relying on traditional datasets, I’ve used ChatGPT and Claude to construct a synthetic index of political violence in the US since 1945. Let me be absolutely clear: this isn’t conventional data. It’s data generated through language models, with all the limitations that implies.

The Methodology (and Its Limitations)

Here’s what I did: I asked both ChatGPT and Claude to generate lists of politically motivated violent incidents since 1945, then had them score each incident’s severity on a scale where 50 represents a “normal” level.

The models assessed both casualties and symbolic significance, and I used them to cross-check each other’s work. I then quality-checked the output myself and categorised perpetrators by political affiliation where this was clearly established.

This approach is, admittedly, unorthodox. Language models are trained on existing texts and may reflect biases in their training data. They might overweight highly publicised events or recent incidents that featured prominently in their training corpus.

The “data” we’re looking at is essentially a structured synthesis of what these models have absorbed about American political violence.

Yet there’s something intriguing here. These models have processed vast amounts of information about political violence – news reports, academic studies, government documents. Their output might capture patterns that traditional datasets miss, though it might also amplify certain narratives or blind spots.

What the Synthetic Data Reveal

With those caveats firmly in mind, the patterns that emerge from this exercise are concerning. The model-generated index shows a clear upward trend in political violence over the past decade.

Looking at the breakdown by perpetrator ideology (where clearly established), the data suggest that right-wing extremist groups have been responsible for the majority of incidents in recent years, though we cannot draw conclusions about today’s attack whilst investigations are ongoing.

The synthetic data align with some empirical observations. Princeton’s Bridging Divides Initiative recorded over 600 incidents of threats and harassment against local officials in 2024 – a 74% increase from 2022. The University of Maryland found that in the first half of 2025, 35% of violent events targeted U.S. government personnel or facilities – more than twice the rate in 2024.

The Charlie Kirk Assassination and Recent Patterns

The September assassination of conservative activist Charlie Kirk marked a particularly dark moment.

The incident followed numerous recent acts of political violence, including the murder of Minnesota Democratic state Rep. Melissa Hortman and her husband, and two assassination attempts on President Trump in 2024.

What the synthetic data reveal is not just increased frequency but a shift in patterns. While overall levels of physical political violence remained low in 2024 compared to years prior, acts of vigilante violence grew as a proportion of all reported incidents.

We’re seeing less organised group violence and more lone-wolf attacks – a pattern that’s harder to predict and prevent.

The Epistemological Challenge

When we use language models to generate “data” about social phenomena, what exactly are we measuring? We’re essentially extracting structured information from the collective corpus of human writing about these events. It’s aggregating distributed information, but through an AI intermediary rather than traditional data collection methods.

This raises fascinating questions.

The models suggest that right-wing extremist violence has been responsible for a fairly large majority of U.S. domestic terrorism deaths since 2001. But how much of this reflects actual patterns versus the way these events are covered and discussed in the sources the models were trained on?

The synthetic data are, in a sense, a mirror of our collective discourse about political violence. They reflect not just what happened, but how we’ve talked about what happened. That’s both a limitation and, potentially, a feature – understanding the narrative landscape around political violence might be as important as counting incidents.

An Experimental Tool

I’ve built an interactive app (using the AI coding tool Lovable) based on this language model-generated violence index.

Users can explore the synthetic data, examine patterns across different time periods and perpetrator groups, and understand the methodology behind it. Think of it as an experiment in using AI to structure historical information rather than a definitive dataset.

The value isn’t in treating this as gospel truth, but in what it reveals about how these events are recorded, remembered, and synthesised in our collective digital memory.

When language models trained on our civilisation’s text output show rising political violence, it tells us something – even if that something is as much about narrative as about underlying reality.

This morning’s tragedy in Dallas reminds us that behind every data point – whether traditionally collected or AI-generated – there are real victims and real consequences. Understanding the patterns, however imperfectly, is the first step toward addressing them.

Try the tool here.





Source link