Fucking traitorous scum

you are viewing a single comment's thread
view the rest of the comments
[–] 48 points 4 days ago* (1 child)

I think it's referring to Linus using AI to develop a python GUI in January for a personal pet project (AudioNoise).

It was the beginning of this cognitive outsourcing that's led to him telling people with entirely legitimate concerns (e.g. that LLM output can't be copyrighted, so it can't be licensed as GPLv2) that he'd ignore them all and to "fork it or walk away", to people who have developed the kernel for many years of their lif.. To now - hiding LLM commits to obfuscate kernel commit info.

I respect and appreciate Linus, but the recent developments highlight a larger (and old) problem of Linux - a single point of failure in Linus and the BDFL attitude. He'll eventually leave the kernel in some way, and while there are drafts and proposals for a succession plan - none have been seriously considered to the point of any action by Linus. He remains the kernel BDFL, and Linux kernel development remains neither a meritocracy nor a democracy.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 4 days ago

    You guys are wrong about copyright.

    It’s going to fall into the same category of pattern making.

    The code itself should never be copyrightable. It’s a series of directions that other human can easily come to on their own and write the exact same way. It should never have been copyrightable, ever. The fact that it is is a privilege you’ve been granted for no good reason. You can rip off fiber artists all day because they can’t copyright their patterns but you can’t rip code? That’s bullshit that has been perpetuated by corporations and needs to end.

    However whatever you make from that code IS copyrightable and immediately granted to your project and the moment you bring commerce into it it’s now an IP. All of this can be enforced and will be enforced. So when it happens remember me babes 💋.

  • source
  • parent