News for hackers. Stuff that matters.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by izacus on Thursday November 10, 2022 @03:31AM (#33543754)
There has never been more support for tightening and enforcing copyright than there is today. This is very unlikely to change due to megacorps like Microsoft, Disney, Apple et.al. having a massive vested interest to use it to extract maximum profits.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by classified on Thursday November 10, 2022 @03:46AM (#33543850)
Copyright protection for the rich and powerful, while those who cannot afford armies of lawyers get their stuff stolen by machine learning models. Sounds credible to me.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by guntars on Thursday November 10, 2022 @04:02AM (#33543959)
I find Copilot most useful for filling out debug statements such as this:

  println(“foo at {:x} is {:?}”, &foo as *const _ as usize, foo);
It almost always writes what I would have. How DARE I steal from open source contributors like that?!
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by 3836293648 on Thursday November 10, 2022 @04:56AM (#33544365)
Given how rust-y that looks, are you aware of `dbg!`? Debug printing + file name + line number and it does it properly to stderr
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by classified on Thursday November 10, 2022 @05:25AM (#33544567)
A human re-using some code according to its license is not the same as an automated machine snorting up all of the code on the platform ignoring any licenses.
Re:An Open Source Lawyer’s View on the Copilot Class Action ... by 6stringmerc on Thursday November 10, 2022 @03:55AM (#33543911)
I’m not rich and powerful but I’m glad Disney is going to destroy MystickInk on principle.

Check out my essay I’ve submitted recently.