Asahi Linux now runs Windows games without a VM, thanks to a page-size patch

> Some time ago, we were made aware of multiple attempts to exploit our permissive licensing to hijack our work, with a direct view to replacing the project and aggressively monetising Linux on Apple Silicon.

Is this referring to Omarchy? Anyone have context? TBH I'm surprised their work was ever MIT-licensed instead of GPL.

The only blocking point for me before I would use Asahi Linux is the support of the USB-C displays. I was considering and reconsidering to install Asahi so many times, but I just cannot give up the ability to plug an external display into my MacBook Air.

I am just surprised that other features like support of the newer CPUs still get a higher priority than this one. I am not complaining or anything, I am not even related to the project in any way, so not in the right place to ask for anything, but I really am surprised that this seems to not to bother most of the users?

> It may surprise some to learn that WINE was originally made available under the MIT licence. The 90s and 2000s were a very different time in the Free Software ecosystem, and permissively licenced projects were viewed by tech companies as free real estate to pilfer and exploit. WINE was not immune to this, and many monetised proprietary forks of WINE were marketed and sold by various bad actors. The WINE development team grew increasingly concerned that these proprietary forks, while well within their rights to exist, would eventually cause so much fragmentation in the ecosystem that WINE itself would become unviable. In 2002, WINE was relicenced under the LGPL to prevent further proprietary forks from being created, and to encourage direct upstream contribution.

> When Asahi Linux was first started, it was with the intent that we develop a Free Software ecosystem for the Apple Silicon platform. To facilitate and encourage the particiation of our friends at the BSDs and other Free Software operating systems, we endeavoured to licence as much of our code as possible under the permissive MIT licence.

> Unfortunately, this is no longer viable. The malicious practices of the 90s and 2000s have reared their ugly heads once again, this time driven in large part by both the insatiable appetite of frontier AI labs for high-quality training data, and militant animosity toward the Free Software community.

> Some time ago, we were made aware of multiple attempts to exploit our permissi […]

honest question - how hard it is to use LLM and tools like REA to reverse engineer MacOS to figure out how its hardware works in terms of getting linux support on such hardware?

I thought it is already a solved problem? with large enough numbers of agents running in parallel reverse engineering, implementing kernel modules, testing in vm etc, the whole pipeline seems to be complete.

Did I miss something here?

Why doesn't the Asahi team just design their own silicon? With AI it is easier than ever. And no this is not a joke.

How to get it fabbed? That's even easier as there are lots of companies with $$$ who'd like to commoditize Apple.

This thread is full of folks saying, "Asahi can't keep up with Omarchy," when Omarchy Mac's own readme[0] states that it is, "Asahi Alarm + Omarchy." That's like bragging that someone sitting on Lebron's shoulders can dunk a higher rim than he can.

[0]https://github.com/omacom/omarchy-mac

Y'all should just let asahi cook. I trust them more to make actual working stable OS than meat proxies.