On mobile I didn't see the full URL, and zoomed before I saw the calendar. My bad.
The author’s blogpost is sloppy and has some signs of being AI written. This kind of bleeds into the main point I’m going to make.
Asahi Linux folks are clearly more conservative and erring on the side of caution, so, this means that the glibness with which the author is treating any of this is probably sufficient cause to refuse his entries. It is unclear if LLMs should be considered a toxic waste dump in terms of trying to maintain a clean room. We have not established a standard. It is clear the author doesn’t think this is a big deal, so that’s one conflict. The other conflict is that it is not clear what their exact interactions with Apple Silicon folks is and their glibness of it doesn’t clarify anything.
If you take a group that is trying to be very careful about the potential legal landmines a still nascent technology has and you get someone that espouses a general glibness about those concerns wanting to merge code…why on earth would you expect that group to accept them as a contributor?
This is not to say this isn’t really cool and a neat use of LLMs, but it is totally understandable why Asahi Linux won’t accept the fruits of this kind of development. If it turns out that Apple can identify its non-OSS code in this, it’ll be a mess.
I mean they are working around and on hardware controlled by a nearly 5 trillion market cap behemoth who has resources on the level of some nation states.
I'd be erring on the side of caution as well if they could hire that many lawyers.
For the lazy.
And they say irony is dead.
I say this from an anonymous account but at least it isn't a throwaway. And at least I have the good taste to feel a little shame for my hypocrisy.
No statute defines "clean room RE" and there's basically no relevant litigation establishing case law.
This "clean room RE" fabrication is also not something so obviously compelling that nobody would ever attempt to challenge it - it's just that nobody has cared to put dollars behind it. IP provenance cases are enormously difficult to prove and are almost always settled ahead of trial. This concept is software engineer folklore more than anything.
I seem to recall DeCSS being the 'hot button' as it was RE'd in a 'non clean' way, the code released, and then a 'clean room' RE could be made from the 'public' info ??
edit: actually, at the time I think there was German law allowing RE for 'interoperablity' or some such. But that was a long time ago so my memory might be off.
It's safest to err on the side of plausible deniability, any proximity to OEM software increases liability if things go wrong.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/lin...
Just call yourself "Idea Llmina" or whatever and let someone else commit it.
The only way to get flawless Linux support is to buy hardware from an OEM that supports Linux well.