Anyone know how long the waitlist is?
GitHub Copilot available for JetBrains and Neovim
131–140 of 446 posts
Re: GitHub Copilot available for JetBrains and Neovim
#132Earlier quoted context omitted.
Except he knows what to look for and how to exploit it. Could lead to easy bug bounty money.
Seems like an exceptionally risky attempt to make money using programming skills. Why not directly add value to the software world?
I'm not endorsing it. FWIW I won't use Copilot and won't add (voluntarily that is ;) bugs in my code to sabotage it.
Re: GitHub Copilot available for JetBrains and Neovim
#133Earlier quoted context omitted.
Legally, it needs to be opt-in in order to protect downstream consumers of code written by Copilot. Copilot sometimes reproduces code verbatim. You can't use open source code except under the terms of the license. Authors whose code may be reproduced by Copilot need to grant a license to downstream consumers, and republishers of Copilot-generated code need to adhere to the terms of that license. Copilot is inserting…
Nope. Copilot users are inserting "ticking time-bombs" into their own codebases. The buck stops with the user, when they use code from any source at all , whether it's their head, the internet, some internal library, lecture notes, a coworker, a random dude of the street, or who knows what else, it their own responsibility to ensure the code they're using has been released under a license they can use. They don't get…
We agree that downstream users who redistribute copyrighted code regurgitated by Copilot are in violation of copyright.
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.
There's a separate question about Microsoft's own liability. When Copilot reproduces open source code without adhering to the terms of the license, that's redistribution and thus copyright infringement. A copyright owner might not be able to get substantial monetary damages, but they ought to be able to get a copyright injunction.
I wonder what happens to Copilot should a Github user secure injunctive relief, forcing Microsoft to exclude their code from Copilot.
Re: GitHub Copilot available for JetBrains and Neovim
#134I've been getting a lot more misses than hits with Github Copilot, even when writing elementary math or utility functions; but despite its error I am nevertheless astonished at its approximation of intent. Very eager to see Github Copilot catchup to some bright line of signal v noise.
I would say the reverse, I’m getting so many hits that I’m mindblown. And when it missed, I can generally still use that and fix the suggestion, as it’s faster.
It's a glorified autocomplete to me. It seems like it feeds me mostly things I'd get from searching Stack Overflow. The first day was pretty interesting but the novelty wore off quickly. You still need to grok what it spews out and see if it's correct.
And the worst thing about that is that you don't get the context of the Stack Overflow threads, where people discuss the impact of the given solution and alternatives. So after a week, off it went for me.
Re: GitHub Copilot available for JetBrains and Neovim
#135Copilot is crazy. The other day, I was writing a Python function that would call a Wikipedia API. I pulled from the internet an example of a GET request, and pasted it as a comment in my code. # sample call: https://en.wikipedia.org/w/api.php?action=query&format=json&list=geosearch&gscoord=37.7891838%7C-122.4033522&gsradius=10000&gslimit=100 Then I defined a variable, base_url = "https://en.wikipedia.org/w/api.php?"…
Bit of a dodgy way to form query parameters though. Other than for a quick script.
How so?
Re: GitHub Copilot available for JetBrains and Neovim
#136Still no way to opt your code out of this. Disgusting.
Yes there is, make your repo private.
Re: GitHub Copilot available for JetBrains and Neovim
#137I hope it will work for the 'standard' vim, so far it reports 'vim version too old', while I'm using the newest vim.
it's said because vim lacks 'virtualtext' feature.
Re: GitHub Copilot available for JetBrains and Neovim
#138Earlier quoted context omitted.
Tried it out for a while, and it's clear that it's trying to get people to be faster at writing boilerplate, not get people to write better code. I'm a bit scared for what this means as I don't think being able to faster write boilerplate is something worthwhile. The example ed_elliott_asc made is one of those examples where instead of fixing things so you don't have to repeat yourself, copilot makes it easy to just…
Writing a slightly abstracted library to handle populating a list isn't necessarily "fixing" something. It might be, for sure, but is going to be very use case dependent, and there are a lot of instances where it's better to have 5, 10, or yes even 15-20+ nearly-identical lines and be done in a minute or two (or 5 seconds with Copilot IME) than spend half a day tweaking test coverage on your one-off library.
> Writing a slightly abstracted library to handle populating a list
> than spend half a day tweaking test coverage on your one-off library
If you need to write a library and spend half a day to populate a list, you have bigger problems than boilerplate.
Nothing wrong with having duplicate lines. The problem becomes when writing those lines become automated so you start spewing those all over the place.
Re: GitHub Copilot available for JetBrains and Neovim
#139Does it relies on a Microsoft-provided API? If it's not offline, the same gotchas as other SaaS apply.