Post B9JSgyeKjypHASfTu4 by lanodan@queer.hacktivis.me
 (DIR) More posts by lanodan@queer.hacktivis.me
 (DIR) Post #B9JMzDwO1m3u51QhTk by foxyloon@blimps.xyz
       1 likes, 0 repeats
       
       @baralheia IMO, forking the kernel and letting that ship burn is the realistic move here. The alternative is to try to take over the organizations around linux development from within, but that's never worked for anyone who didn't have an infinite money glitch backing them. The techbros have about 3-5 years of riding out this AI bubble, so they have billions at their disposal. No way of fighting that head-on.Frankly, it'll be easier to fork the kernel and poach the code maintainers who don't want anything to do with the AI nonsense affecting their workflows. Linus himself was saying "if you don't approve, then fork the kernel", so why not do exactly that? That's what he did when he first invented linux after the BS the Unix team was pulling back in the 80s.
       
 (DIR) Post #B9JNQQttx1Sa5qF2Js by lanodan@queer.hacktivis.me
       0 likes, 0 repeats
       
       @linear @baralheia @foxyloon https://cip-project.org/ I guess?Which is a Linux Foundation project, no way it will not also go slop if it hasn't already.
       
 (DIR) Post #B9JSgyJPzk607asmIq by foxyloon@blimps.xyz
       0 likes, 0 repeats
       
       @lanodan @baralheia @linear Those get small security patches but are otherwise left alone, though. :blobfoxthinking:
       
 (DIR) Post #B9JSgyeKjypHASfTu4 by lanodan@queer.hacktivis.me
       0 likes, 0 repeats
       
       @foxyloon @baralheia @linear Which doesn't really changes things much though?In fact reminds me of a weirdly failed backport from I guess greg k-h few days ago: https://social.treehouse.systems/@mgorny/117051630097043064