I hope I never again have to work on a codebase/language where copilot would be worth subscribing to.
Unfortunately, there is no way I can hope for that much…
So yes, please, take my money and do All my boilerplate lol
771–780 of 796 posts
I hope I never again have to work on a codebase/language where copilot would be worth subscribing to.
Unfortunately, there is no way I can hope for that much…
So yes, please, take my money and do All my boilerplate lol
Earlier quoted context omitted.
This take is too reductionist. Every website ever has a boring unit test called “Is it up?” where you check if the site is still working after a deployment. Boring and repetitive but of infinite value if you can detect early that your deployment broke something. If a boring/boilerplate unit test like this can deliver value, other b/b unit tests are probably going to similar impacts and hence, saying they all “decreas…
> Every website ever has a boring unit test called “Is it up?” Yeah, and it should come almost automatically from the tooling. If you are writting this, you have a tooling problem.
Goal of library/language/framework designers: limit boilerplate and unnecessary code
Goal of tool/IDE designers: make it easy to not spend time on boilerplate and unnecessary code.
Both sides have built in limitations that will keep them from completely solving the problem. Terse, highly DRY code tends to also be highly abstracted and hard to read, with a lot of implicit behavior. On the other side, large amounts of generated code lead to tool lockin and cruft accumulation.
Earlier quoted context omitted.
Didn't OSS maintainers already voluntarily approved such uses when they published their work under an OSS license? One fundamental aspect of being open source is not limiting the purposes of use. If we now say that "code-generation AI training" is not allowed without prior approval (in addition to the license itself), then it's not open source anymore...
I approved some of my code for being reused under the terms of the AGPL. Co-pilot is very welcome to scan it and generate derivative AGPL code. If I write AGPL code, and co-pilot scans it and makes a very similar program to it for a FAANG, who then proceeds to compete with my open-source tool by using the creative ideas generated there-in, but with a proprietary tool, that's not very fair. That's why I chose the lice…
I really like copilot, but my outside of the content being generated it still feels a bit slow and somewhat hacked into vscode. It sometimes interferes with regular "intellisense suggestions" as well. I've been in the beta since almost the beginning I have not really seen much improvement on the frontend side. Since its release, the changelog only mentions 10 small (or so it seems) improvements https://marketplace.vi…
I've been using Copilot for a few months and... Yeah, it makes mistakes, sometimes it shows you i.e. the most common way to do something, even if that way has a bug in it. Yes, sometimes it writes a complete blunder. And yes again, sometimes there are very subtle logical mistakes in the code it proposes. But overall? It's been *great*! Definitely worth the 10 bucks a month (especially with a developer salary). :inser…
What would be your estimate for how much time it saves?
For example, I just had to convert some OCaml code to Rust. I wrote the first few conversions, and then I would just paste the OCaml code in a comment, and it would auto-complete the equivalent code in Rust. I just had to check that it was correct, which it was most of the time, rinse and repeat and wow. One would have to be blind to not find copilot impressive, really, it's the future.
Earlier quoted context omitted.
> Anything "may" be possible. But it probably won't be worth that much. I'd suggest to get more information about the repercussions associated with appropriating GPL code into proprietary closed source. This is a big deal. You may have to license your entire codebase under GPL if you incorporate GPL code and distribute it.
> You may have to license your entire codebase under GPL if you incorporate GPL code and distribute it. I would suggest that you actually take your own advice and get more information yourself. No license can force you to release your code. Nope, not even GPL. Instead, what a rights holder can do, is sue for damages for the copyright theft, for not following the license. They can't force you to follow the license. In…
I did not say it forces you to distribute it. That's absurd.
What I said is: "if you incorporate GPL code and distribute it"
If you do those two things, yes, you have to license your code under GPL.
It's not me saying, please take a look at Section 5-b and 5-c of the license. [1]
I've been using the beta since last year and I love it. I think most of the people complaining about it either haven't used it, or are judging it on its most verbose guesses. That's not what I use it for mostly. For me, it's just a really, really good autocomplete. It's best for things with common patterns and APIs. But hey, they're common so I write them a lot. Boring stuff like creating a Response object, adding th…
How much time would you say it saves you per day? Ie. how much more productive does it make you? I’m curious whether we’re talking 5% or 30%.
I assume that Copilot uses open source projects on GitHub to “learn” what to suggest. Some of these projects might be under, say, GPL v3. A developer uses Copilot for a commercial project and Copilot insert a complete function from a GPL v3 code into this project. Someone notices this and sues the commercial project for breaking GPL v3. Will GitHub pickup the tab?
I've been using Copilot non-stop on every hobby project I have ever since they've let me in (2021/07/13) and I am honestly flabbergasted they think it's worth 10$/mo. My experience using it till this day is the following: - It's an amazing all-rounder autocomplete for most boilerplate code. Generally anything that someone who's spent 5 minutes reading the code can do, Copilot can do just as well. - It's terrible if y…
Guys you're getting a lot of bad comments for one simple reason. You failed your delivery. 1) You should have managed the expectations of the users in a better way. Tell them it will become a paid feature from the begining, so nobody gets surprised 2) The way everyone unsderstood this today was too aggresive. An infinite warning in visual studio saying "hey, i've stop working, please sign up and pay or uninstall me".…