Live data from Hacker News

GitHub Copilot is generally available

github.blog

541–550 of 796 posts

Re: GitHub Copilot is generally available

#541
post #193

The main page [0] shows you awesome demos, but also its weaknesses in the very first example. It doesn't encode the url encoded body properly: > body: `text=${text}`, So it breaks if the text contains a '&' and even allows parameter injection to the call of the 3rd party service. Isn't that critical on a sentiment analysis API, but could result in actual security holes. I hope the users won't blindly use the generate…

that's why it's called copilot and not autopilot

Re: GitHub Copilot is generally available

#542
post #353

Earlier quoted context omitted.

I wholeheartedly agree with your analysis, but feel like it’s ignoring the elephant in the room: writing code is not the bottleneck in need of optimization. Conceiving the solution is. Any time “saved” through Copilot and it’s ilk is immediately nullified by having to check it’s correctness. From there, the problem is worsened by the Frankensteinesque stitching together of disparate parts that you describe. I can’t i…

> I wholeheartedly agree with your analysis, but feel like it’s ignoring the elephant in the room: writing code is not the bottleneck in need of optimization. Conceiving the solution is. I dunno about this. I know the received wisdom is that "writing the code isn't the hard part", but I think reality is more like "writing the code is only one of the hard parts". There's an awful lot of badly-written code, or code whi…

Writing the code is the hard part mainly inasmuch as it forces you to concretize and clarify previously vague notions. In that sense, it's hard to separate "conceiving the solution" from "writing the code," unless you're perhaps one of those rare geniuses who are simply able to dictate ideas fully formed in their head (I'm thinking of the scene in Amadeus when Salieri examines some clean, uncorrected sheet music and is then shocked to discover that Mozart doesn't make copies and he's holding originals).

Re: GitHub Copilot is generally available

#543
post #226
post #195

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…

"how to put a sentence together describing the rules, it absolutely doesn't actually understand how "Chii" melds work" The more experience I get with GPT-3 type technologies, the more I would never let them near my code. It wasn't an intent of the technology per se, but it has proved to be very good at producing superficially appealing output that can stand up not only to a quick scan, but to a moderately deep readin…

After looking at lots of these new models, I've come to the conclusion that they're all basically weighted gibberish generators that produce output not entirely dissimilar to old fashioned hidden markov chains -- just more sophisticated. The corpus is larger and the weighting scheme is much more sophisticated (i.e. you can use prompts), but at the end of the day they're sort of just barfing out nonsense that does a better job at tricking humans into thinking they're doing something smart. These models have really just introduced the concept of differing "qualities" of gibberish on a sliding scale from

   random words ---> markov models ---> transformer ---> human writer
Inevitably, users of these kinds of models want them to produce more and more specific output to the point that they really don't want what the models produce and instead are just trying to get a computer to write stuff for them that they want. Eventually all the tuning and filtering and whatnot turns into more work than just producing the output the user wants in the first place.

It's just a room of monkeys banging on typewriters at the end of the day.

Re: GitHub Copilot is generally available

#544

Earlier quoted context omitted.

Probably not exactly what you're looking for, but Warp (a new terminal client) has "AI Code Search" built in that's powered by GPT-3. Quite useful for someone like me who tends to avoid the terminal when I can. https://www.warp.dev https://docs.warp.dev/features/ai-command-search

There's this cool blog on them testing it out against popular git commands: https://www.warp.dev/blog/replace-git-cheat-sheet-ai-command...

them as in that’s you :)

Re: GitHub Copilot is generally available

#545
post #382

Like many people I thought Copilot was neat but ended up uninstalling it because it caused more problems than it solved. Reading the comments here, it seems that most of the people who get value out of it would be better served creating a set of snippets. If all you need is to fill in boilerplate all the time or repeat general test structures but with different arguments, just make a snippet. Every major code editor…

Or better yet, save the snippet as a function/procedure in the code, and avoid needless duplication (DRY/Occam's razor).

You can take snippets with you from job to job tho.

Re: GitHub Copilot is generally available

#546
I’m so ambivalent about this.

I was excited when it came out, but it ran slowly and annoyingly (crashes) and I gave up.

I already have a jetbrains license; when they release a similar feature I’ll consider uping my subscription to get it.

As it stands… eh. It’s not that great. I couldn’t really be bothering to continue using it for free, I’m not gonna pay for it.

Re: GitHub Copilot is generally available

#547

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…

I really don't like it.

I find I spend my time reviewing Copilot suggestions (which are mostly wrong) rather than thinking about code and actually doing the work.

Re: GitHub Copilot is generally available

#548
I don't understand the argument that they analyzed all the code from their users, used it to train their service, and are now charging for the service.

Do people want to see ads instead?

Or would they be ok paying for Google search (another service trained by all the information we willingly volunteer to them)?

Copilot adds tremendous value and they are justified charging for it.

Re: GitHub Copilot is generally available

#550
post #36
post #3

What's the criteria for being considered "a maintainer of a popular open source project"? They never actually publish the criteria anywhere from what I can tell. They just say visit the subscription page and if you are eligible it should be available to you and if you see a charge then you are not eligible. I think though they should still be transparent about what their metric is for determining popular projects on…

At a minimum, 4.3k stars is not enough, because I don't qualify.

Someone from GitHub reached out to me because of this comment and said they were fixing it. The problem is that Racket's license file isn't simple enough for their automated tools.
Post reply on HN