As you’ve likely heard by now, hell froze over, pigs got their pilot’s licences, and Fortnite is finally coming to Linux. Gamers rejoice! Maybe we’ve finally reached the year of the Linux desktop, at last. And, all jokes and tongue-in-cheek histrionics aside, we actually might be there. For real this time.
It’s tempting to attribute this to people getting fed up with Microsoft Windows and jumping ship to the nearest life raft. Or perhaps Linux has finally matured enough to be a viable alternative, something I’ve argued for years myself. Neither explanation is wrong, but both miss the bigger picture.
What we’re seeing is the forest, not just the trees: corporations and individual users choosing Linux for very different reasons, with those choices collectively changing the software landscape.
I won’t lie. I was pretty ecstatic when Epic Games announced a native Linux preview of its launcher, with Fortnite set to follow once its anti-cheat work is ready. For years, Fortnite has been one of the most prominent examples of a game Linux users couldn’t play locally. That barrier is finally on its way down, and it’s a win worth celebrating.
But as the details became more abundant than the hype, something else caught my attention.
An Epic win, with an asterisk
Naturally, a few Linux and open-source diehards declared that Epic’s launcher and Fortnite “aren’t welcome here!” As one does in this community. We’ll sigh and leave them to their corner.
My concern was different: the quality of what Epic released, and what that might say about how major companies approach platforms they’ve historically treated as secondary.
Epic proudly described its new launcher preview as “vibe coded”. That isn’t inherently a problem. But the preview also arrived with some conspicuous bugs, including Linux-specific interface problems. Granted, it was a preview, the developers supervised the AI-assisted work, and Epic has been fixing issues at an encouraging pace.
Still, it raised a familiar question. Why does software from a company with this level of engineering expertise sometimes feel less carefully prepared when it arrives on Linux?
This isn’t a demand for flawless preview software, nor an argument that AI has no place in development. It’s a question about priorities and the standards we consider acceptable when a company finally decides a previously neglected platform is worth supporting. I’ve seen this pattern throughout my years using Linux as my daily driver. When a major vendor brings its software to an open platform, it doesn’t always bring its A game. Worse, when the result disappoints, Linux itself is often blamed.
I’ve written before about the manufactured myth of Linux support: vendor decisions have a habit of being presented as platform inadequacies, even while the same companies rely on open-source technologies behind the scenes.
That doesn’t mean Linux is perfect. Fragmentation, compatibility and security requirements pose genuine challenges. But those challenges don’t explain every shortcoming, nor do they absolve companies of responsibility for investment and quality assurance.
And that brings us to the part I find most revealing.
The chicken, the egg, and the leap that wasn’t
Companies could have made many of these shifts years ago. Linux’s old chicken-and-egg problem was never purely technical: companies wouldn’t invest without enough users, and users wouldn’t switch without the software they needed. For decades, that cycle made a convenient explanation for why things couldn’t change. Then Valve decided to do something about it.
Valve didn’t invent Linux gaming, nor did it act alone. Wine, CodeWeavers and open-source developers had been laying the groundwork for years. But Valve invested in that foundation, helped drive Proton and SteamOS, and showed what happens when a company chooses to help create the market it wants to serve.
Was it a leap of faith? In a sense, yes.
But it was also a strategic decision to reduce dependence on Windows and invest in a platform that already powered much of the industry behind the scenes. Crucially, Valve also put a Linux-based gaming experience in front of a mainstream audience through the Steam Deck. That made the possibilities harder to dismiss. Linux didn’t suddenly become capable overnight; a company had finally taken on the commercial risk of making it accessible.
Now that Valve and others have demonstrated the value of that investment, more companies are recognising an opportunity that was never entirely out of reach.
The question was never just whether Linux was ready for the industry, but whether the industry was willing to invest in Linux.
When the dog and the tail start wagging each other
The software market isn’t shaped solely by what consumers need. It’s shaped by what companies make available, what they persuade us is necessary, and which platforms they present as legitimate places to get work done. For years, that favoured proprietary ecosystems. A lack of software reinforced the belief that alternatives weren’t viable, which in turn justified withholding support. Quite the convenient cycle, isn’t it?
But something unusual is happening now: industry and consumer interests are pushing in the same direction, even though their motivations are often at cross-purposes.
On one side, companies are moving away from treating individual operating systems as the centre of everything. Services, subscriptions, cloud platforms and streaming increasingly follow the customer. From that standpoint, supporting more operating systems isn’t necessarily an embrace of openness. It’s good business.
On the other side, consumers are becoming increasingly tired of ads everywhere, subscriptions for everything, invasive data collection and software that feels less like something they own than something they’re merely permitted to use. For many, Linux offers a way to reclaim some independence. Corporations want greater reach. Consumers want greater freedom. Both are helping to dismantle the barriers that once kept desktop computing so firmly divided.
That’s also why I wouldn’t confuse this shift with an industry-wide conversion to open-source principles. A company can be perfectly happy to support Linux while keeping its users locked into a proprietary service. The operating system may become less important to its business precisely because the account, subscription or streaming platform becomes more important instead.
The dog and the tail are finally wagging each other.
But there’s another question worth asking: who gets to benefit from this new enthusiasm for Linux?
Follow the money
Consider Omarchy, a relatively young and controversial Arch-based distribution whose foundation has attracted more than $23 million in pledges and donations, including in-kind computing resources and AI credits.
In one sense, on paper, it's encouraging to see serious money flowing into Linux, at least in principle, and the foundation also says it intends to support upstream projects it depends upon. But I can’t help noticing how quickly enormous commitments have materialised for a fashionable newcomer, when established projects (with arguably "cleaner" foundations) have spent decades struggling for considerably more modest support, sometimes receiving none at all.
The contrast is especially striking with DigitalOcean. In September, it committed $3 million over three years to Omarchy’s foundation. Shortly afterwards, projects such as Textpattern learned that DigitalOcean was ending its wider Open Source Credits programme, on which they had relied for years. That doesn’t establish that one decision caused the other. But it does raise an uncomfortable question: why can the industry suddenly mobilise millions for certain projects while longstanding contributors struggle to retain the support they already have?
The issue isn’t that Omarchy is receiving funding. It’s what the contrast reveals about priorities, influence and whose work the industry chooses to value. And even if some of that funding eventually reaches upstream projects, it shouldn’t require the arrival of a trendy new distribution for the underlying ecosystem to be considered worth sustaining.
The next age of software
Meanwhile, users aren’t waiting patiently for companies to grant permission to use their preferred platforms. Communities continue to build compatibility tools, improve open-source applications and make software work where they want it to work. It’s not all AI-driven, either. Much of this progress rests on years of human ingenuity and persistence.
The industry is responding. Some companies are catching up, others are shaping up, a few seem determined to shake customers down (looking at you, Sony), and others are reconsidering their place in the market altogether. Of course, cross-platform availability doesn’t automatically mean openness. A subscription service running on Linux can still lock users into accounts, restrict choices and collect their data. New investment can improve an ecosystem without necessarily embracing its values.
But the more users demonstrate that they’re willing to move, adapt and build alternatives, the harder it becomes to insist that one particular operating system is the price of participation. Plus, the more companies support Linux, the more reasonable it becomes to expect that support to be good, not merely present. Support should mean quality, compatibility and ongoing investment, not just another logo on a platform list.
That’s why I’m both excited and sober about Epic’s announcement. Don't get me wrong: it’s a genuine win, but the bigger achievement isn’t simply having another large corporation betting on Linux. It’s having more choice, fewer artificial barriers and better access to software wherever people choose to use it. In some ways, this feels like a software-industry mass extinction event. Old assumptions are collapsing, the landscape is changing, and we may lose some corporate and community-driven megafauna along the way.
But extinction events also create room for new forms of life to flourish.
We may be heading towards a very different relationship between creators, companies and consumers. It won’t always be pretty, and the motivations won’t always be noble. Still, if the result is an ecosystem where freedom, quality and choice can coexist, even if the industry has to be dragged there by force? I’d call that an age of epic wins, even if some take a bit longer than a fortnight.
Practical Tip: Support what makes it possible
The next time you discover a Linux app or project you're excited about, take a moment to find out what it depends on. There may be libraries, tools and volunteers behind the scenes doing work that rarely makes the headlines.
If you can, support one of those projects. A useful bug report, some documentation, a recommendation to someone who needs it, or even a small donation can make a difference.
It's great to celebrate the big wins. Let's also remember the people and projects making them possible.
If you want to stay in this lane
I've written some related articles in this series that you might find interesting if you liked this one:
The Manufactured Myth of Linux Support
Why software availability and anti-cheat support are so often treated as Linux limitations when vendor decisions are part of the story.
What happens when open-source takes itself seriously?
A look at how Linux and open-source projects are raising the bar through usability, infrastructure and long-term investment.
Open-Source Owes Us Nothing, And That's Good
Why open-source independence matters, and why the contributors behind the software we rely on deserve support and respect.
Working with us
At RolandiXor Media Inc., we blend design and open-source thinking for our clients.
Elsewhere
- Mastodon: mastodon.social/@rolandixor
- Threads: @rolandixor
- X: @rolandixor
Support this work
If this writing has been useful and you’d like to help sustain it:
→ https://ko-fi.com/rolandixor
Catch you in the next Roll Out!
Comments