Haiku OS is similarly hard-line about this, and is also starting from the point of an extremely clean codebase.
Neat stuff, though I can't say AI policy is the biggest priority when I choose projects to use, plenty of projects are using it in a measured and sane way without needing a complete prohibition.
As long as Linux doesnt fully commit to vibe coding i dont see a reason to switch, but if it ever does its essentially proprietary software that only AI companies with their frontier models can modify, so i hope they dont
Haiku OS is similarly hard-line about this, and is also starting from the point of an extremely clean codebase.
Neat stuff, though I can't say AI policy is the biggest priority when I choose projects to use, plenty of projects are using it in a measured and sane way without needing a complete prohibition.
> I can't say AI policy is the biggest priority when I choose projects to use
I wouldn't expect it to be on HN. This place is a den of AI iniquity.
But for a lot of people out there, slop-free software is an increasingly rare and desirable thing.
Oh, cool, thanks for sharing this -- it's one of mine.
As long as Linux doesnt fully commit to vibe coding i dont see a reason to switch, but if it ever does its essentially proprietary software that only AI companies with their frontier models can modify, so i hope they dont
Given the linux kernel is being forced to remove AI attribution notes. Welcome to the end times.
https://www.phoronix.com/news/Linux-Dropping-Assisted-By-Req
Every project is AI free, until it's not.
NetBSD will soon realize there's very limited value, to put it nicely, in shipping code full of bugs that an LLM would quickly find.
Either that, or a fork that anybody sensible within NetBSD will embrace.
This is a project that insists on using CVS so yeah, it's not surprising that they do not try the most modern development techniques