3 ms·

I find it extremely funny that programmers are upset that their own work is being used as fuel for the same kind of software exploitation that they have, as a g

I find it extremely funny that programmers are upset that their own work is being used as fuel for the same kind of software exploitation that they have, as a group, gleefully and with little regard for the moral rights of creators inflicted on others. When it was books, films, videos, news articles, journal articles, blog posts, photographs, extremely private personal data, music, art and other creative works being hoovered into the giant AI exploitation cloud in the sky, and non programmer creatives complained, they were generally labeled as luddites, trolls, whiners, maladapted (“learn to code”), and just generally ignorant worthless trash. Now that it’s happening to you oh boy do you care.

Gigachad 4y ago
analog31 4y ago
Indeed when it was recorded music, the musicians were the ones being blamed for having "the wrong business model" or an inconvenient distribution mechanism.
langsoul-com 4y ago
Every group cares about their own interests first, whilst everything else is just progress.
metalrain 4y ago
I don't really mind copyright at all. But I'm worried automation tools take away my (false) sense of control and the art of coding. Why care about variable naming since AI will generate most names anyway, why care about common libraries if you can always get good implementation for specific use case in a second or two? I know these small details don't matter in the big picture, code exists to do something and if it does, it doesn't matter how it was made.
- BeefWellington 4y ago
  The library point is especially instructive IMO. Copilot introducing "learned" security issues, for example, is a problem separate from the copyright risk. Currently, it's often a matter of updating a dependency to patch things away. How do you do that when you barely understand the code it helpfully generated for you? People will jump to say "well that's using it wrong" but the reality is if you allow this in your org people will use it this way.
deleted 4y ago
[deleted]

Gigachad 4y ago

analog31 4y ago

Indeed when it was recorded music, the musicians were the ones being blamed for having "the wrong business model" or an inconvenient distribution mechanism.

langsoul-com 4y ago

Every group cares about their own interests first, whilst everything else is just progress.

metalrain 4y ago

I don't really mind copyright at all. But I'm worried automation tools take away my (false) sense of control and the art of coding. Why care about variable naming since AI will generate most names anyway, why care about common libraries if you can always get good implementation for specific use case in a second or two? I know these small details don't matter in the big picture, code exists to do something and if it does, it doesn't matter how it was made.

BeefWellington 4y ago
The library point is especially instructive IMO. Copilot introducing "learned" security issues, for example, is a problem separate from the copyright risk. Currently, it's often a matter of updating a dependency to patch things away. How do you do that when you barely understand the code it helpfully generated for you? People will jump to say "well that's using it wrong" but the reality is if you allow this in your org people will use it this way.

deleted 4y ago

[deleted]