Gravity Linux and Asahi Linux are two independent projects working towards the shared goal of a strong, open OS ecosystem on Apple Silicon devices. Gravity Linux was initially forked from Asahi Linux over differences in policy, namely regarding LLM use. We have tremendous respect for the Asahi Linux project and emphasize our shared goal of running Linux on Apple Silicon.
OP is the same poster from https://news.ycombinator.com/item?id=49717638 who was noted as having been banned from Asahi Linux over hiding use of LLMs (doesn't seem to be any disagreement about this) and accusations of having Apple proprietary knowledge (challenged by OP).
I disagree with this also, but the latter was so obviously wrong that I figured I should leave a reply. We are separate projects and what Asahi does is their business, our interactions will be in upstream projects and follow upstream guidelines.
From a brief look, it seems separate from Asahi, although it builds on some of Asahi's existing work. I'm still not clear why it needed to be a separate project rather than contributing M4 support upstream. Could be a good reason, but it does look a bit duplicative at first glance.
Is this related to Asahi Linux in any way? Or is it a completely separate project for some reason?
Seems to be 100% entirely different, as Asahi uses Arch, this is on Fedora.
https://gravitylinux.org/about/
OP is the same poster from https://news.ycombinator.com/item?id=49717638 who was noted as having been banned from Asahi Linux over hiding use of LLMs (doesn't seem to be any disagreement about this) and accusations of having Apple proprietary knowledge (challenged by OP).
I disagree with this also, but the latter was so obviously wrong that I figured I should leave a reply. We are separate projects and what Asahi does is their business, our interactions will be in upstream projects and follow upstream guidelines.
From a brief look, it seems separate from Asahi, although it builds on some of Asahi's existing work. I'm still not clear why it needed to be a separate project rather than contributing M4 support upstream. Could be a good reason, but it does look a bit duplicative at first glance.