Earlier quoted context omitted.
Copilot is also almost certainly going to become better. For example, NVIDIA's DLSS was viewed as a failure at launch, but now it's almost magic in terms of offering better results at a lower performance cost.
Better at issuing haphazardly modified boilerplate that already exists... the real costs of writing code are about carefully choosing how pieces will fit together and deciding on minutae with that in mind. Copilot is the antithesis of designing good software.
Is GitHub Copilot a blessing, or a curse?
141–150 of 201 posts
Re: Is GitHub Copilot a blessing, or a curse?
#142Copilot was made from stealing code on Github, ignoring the licenses set on repos such as e.g GPLv2, using AI as a trick to license-launder code. Copilot has announced their plans to become a paid service. So this product that would not be possible without public, open-source code will itself be non-public, closed-source, closed-data. It is extracting value from the commons and funneling it to a private company.
Re: Is GitHub Copilot a blessing, or a curse?
#143Writing code is, uh, not remotely the hardest part of software development. Maintaining it is.
What you say here is true. Writing code is not remotely the hardest part of software engineering. But that does not mean that there is zero value in making it easier.
Shifting gears is not remotely the hardest part of safely driving a car. Yet automatic transmissions are a nice feature for tons of people.
I do not understand this dismissal based on the fact that copilot does not completely revolutionize software engineering in a way that no other product has ever come close to doing.
Re: Is GitHub Copilot a blessing, or a curse?
#144Re: Is GitHub Copilot a blessing, or a curse?
#145Earlier quoted context omitted.
Ha, I ranted about this two weeks ago. https://news.ycombinator.com/item?id=27724969
This is very true, and much like Tesla getting away with it for years (up until recently), GitHub will get away with this for a while as well. And so will the media decrying shit like "Is this the end of developers?!?"
Yeah, CoPilot already replaced my job. I used to be the office copypasta, going around to my coworkers desk all day long to fix their problems by googling them, then pasting in the first snippet to pop up. It didn't matter if the language matched or not, it was more the thought that counted. Now I've had to get a job as a loan rejection stamper at my local bank. It's not nearly as fun or exciting, but at least my effort makes a difference now. A big difference.
Re: Is GitHub Copilot a blessing, or a curse?
#146Re: Is GitHub Copilot a blessing, or a curse?
#147Earlier quoted context omitted.
No part of any open source license says I have to like companies that extract billions in value from open source projects without contributing back to the project. My opinion is simply that once you get to a few million in revenue putting a few thousand back in to the code that got you there is a decent thing to do, and if you don't then you're not very nice. The fact that the license allows you to do this is great;…
GPL asks to release back changes to code made by a company, for which the company paid already, i.e. it's almost zero price for the company, and just look how much companies are afraid to donate zero ($0) worth of code back to the opensource project and prefer to pirate it instead, including such mega-rich companies as M$.
Only if the code is distributed. SaaS can be (and is) used to get around this.
Re: Is GitHub Copilot a blessing, or a curse?
#148There's an interesting section that talks about what you want from a pair programmer - questioning your assumptions, spotting errors, debating design with you, etc, and how Copilot doesn't do this, but instead just spits out the code it thinks you want. That made me think that, when using Copilot, the human is actually the copilot. You're the one spotting bugs, picking different designs, and so on. I also think the d…
Re: Is GitHub Copilot a blessing, or a curse?
#149There's an interesting section that talks about what you want from a pair programmer - questioning your assumptions, spotting errors, debating design with you, etc, and how Copilot doesn't do this, but instead just spits out the code it thinks you want. That made me think that, when using Copilot, the human is actually the copilot. You're the one spotting bugs, picking different designs, and so on. I also think the d…
You might want to take a look in https://www.tabnine.com/