Wait, they got Tim Pope on the case for the Neovim plugin? Amazing, I'm positive it'll work beautifully. For those who don't know, he's essentially the godfather of vim plugins - I even have an entire 'tpope section' in my init.vim
GitHub Copilot available for JetBrains and Neovim
281–290 of 446 posts
Re: GitHub Copilot available for JetBrains and Neovim
#282Earlier quoted context omitted.
>It doesn't seem to me as though the distinction between "Copilot reproduced the code and the engineer copy/pasted/saved it" versus "Copilot inserted the code" is crucial. Is Google responsible when they index licensed code, then others steal it? It's surely the liability of the programmer to "check" (Not really sure how this would work, either).
What matters is that users of Copilot (the "others" who "steal it" in your scenario) are liable for infringement. That renders Copilot impractical as a tool for production use, regardless of whether Microsoft has any liability.
Re: GitHub Copilot available for JetBrains and Neovim
#283Earlier quoted context omitted.
This reaction is why we can’t have nice things :( after trying copilot I’m convinced that this kind of feature is going to bring the world to a next phase. Open source was part 1, this is part 2.
I legit cant tell if the github fanboyism is this real or if this is just a typical product launch astroturfed comment thread
Re: GitHub Copilot available for JetBrains and Neovim
#284Earlier quoted context omitted.
I legit cant tell if the github fanboyism is this real or if this is just a typical product launch astroturfed comment thread
The new generation of "brogrammers" destroying the libre software from the inside. In the 90's we would kick these "brogrammers" out in a breeze.
Re: GitHub Copilot available for JetBrains and Neovim
#285Earlier quoted context omitted.
This reaction is why we can’t have nice things :( after trying copilot I’m convinced that this kind of feature is going to bring the world to a next phase. Open source was part 1, this is part 2.
I understand a lot of people are ok with this and that's fine. There's still no good reason I cannot opt my code out of it.
Re: GitHub Copilot available for JetBrains and Neovim
#286I’ve been using this for weeks and it blooooows my mind. It comes up with crazy recommendations, just yesterday I wrote this big ass logic to do something, then I wanted to move that code to a function so I wrote the function name and I kid you not copilot suggested a one-liner that worked… the thing is so useful and I’m not writing simple code (writing cryptographic code). And when it’s not doing that at the very le…
> writing cryptographic code Delegating the implementation of something that you are notoriously never supposed to roll your own, to a text generator AI.... What could possibly go wrong?
Re: GitHub Copilot available for JetBrains and Neovim
#287I’ve never understood the value proposition for Copilot. In terms of difficulty, writing code is maybe on average a two out of ten. On average, maintaining code you wrote recently is probably a three out of ten in terms of difficulty, and maintaining code somebody else wrote or code from a long time ago probably rises to around a five out of ten. Debugging misbehaving code is probably a seven out of ten or higher. Gi…
Re: GitHub Copilot available for JetBrains and Neovim
#288Earlier quoted context omitted.
Possibly yes, if you're only contrasting it with being able to be faster. I mean, it's sort of a false dichotomy -- it's omitting a "default speed" for writing boilerplate that is neither enhanced nor impeded. the potential issue with an enhanced speed for writing boilerplate is that it means that there'll just be more and more boilerplate to maintain over time, and it's not clear what that cost over time will be. Ho…
> I mean, it's sort of a false dichotomy -- it's omitting a "default speed" for writing boilerplate that is neither enhanced nor impeded. I'm not sure. I think that understanding is omitting a "default amount" of boilerplate that will have to be written regardless of one's individual preference that is really a function of the language / framework of choice, the existing codebase and the problem at hand. Removing tha…
An impedance would be something to adjust the status quo in a negative direction e.g., a hardware failure
Re: GitHub Copilot available for JetBrains and Neovim
#289I’ve never understood the value proposition for Copilot. In terms of difficulty, writing code is maybe on average a two out of ten. On average, maintaining code you wrote recently is probably a three out of ten in terms of difficulty, and maintaining code somebody else wrote or code from a long time ago probably rises to around a five out of ten. Debugging misbehaving code is probably a seven out of ten or higher. Gi…
It's night and day if you have it enabled or not. There's just no question about the value proposition once you start using it.
I mean, you can tell comments here from people who have actually been using it, and people who have not tried it.
Re: GitHub Copilot available for JetBrains and Neovim
#290Earlier quoted context omitted.
Copilot also optimizes for speed to a degree. It's akin to advanced auto complete. IntelliJ auto-completion is great. As much as it pains to say this, I don't think I will be as effective writing Java in Vim as much as I am with IntelliJ. The key differentiator is the auto complete speed. Copilot I feel is just auto complete on steroids. It may not be perfect yet, but there is definitely a problem it solves.
Have you used it? My experience was quite atrocious. Copilot is not auto complete. It’s nonsense. I attempted to use it continuously for three weeks. I tried because I know someone who built it and I wanted to give them the benefit of the doubt. It never prompted me with any code that was useful. It only ever slowed me down and caused me frustration. It’s nothing like Intellisense. It’s just trash.
> It’s just trash
I have a hard time relating to this kind of experience considering how useful it has been for me. What language are you writing in btw? When I use it for OCaml it's not that useful, perhaps because there isn't as much OCaml code to learn from :D