Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GitHub Copilot X – Sign up for technical preview

github.blog

Post reply on HN
Print view View original

171–180 of 771 posts

Re: GitHub Copilot X – Sign up for technical preview

#171

Post by fn-mote »

hu3 wrote: post #130

Scary. For the first time in my life, I feel like my expertise is at risk of being rendered obsolete. Maybe not this year, but the writing is on the wall. Soon coding without an AI will feel as antiquated as delivering food by horse. And resistance is futile because markets will punish those who refuse. We'll probably need less and less developers as AI advance. Just like we need less manual labor in farms today. And…

> For the first time in my life, I feel like my expertise is at risk of being rendered obsolete. Maybe not this year, but the writing is on the wall.

My expertise is in designing, understanding, and debugging complex systems. I will just apply my expertise to the AI.

Another angle: just think of how many mom and pop shops are still contracting out to get web sites, and not getting what we consider quality. Now maybe you're going to see a larger and larger gap between F500 companies and the rest (surely you do already), but playing out the consequences is a long and interesting story.

> coding without AI will feel as antiquated and inefficient [...]. And resistance is futile because markets will punish those who refuse.

Fortunately, the "punishment" by the market will just be reduced salaries. Move out of the Bay Area now. :)

> And coding is just one of the many applications where AI an replace brains.

And writing about those is interesting. With the development of DALL-E (etc), I would say coding isn't even the primary interesting application. (If "it's not AI", whatever... that's not the point.) Or not yet.

Re: GitHub Copilot X – Sign up for technical preview

#172

Post by mistrial9 »

ilovetux wrote: post #131
ren_engineer wrote: post #13

Microsoft really seems to have wrapped up the developer ecosystem with VS Code and the Github acquisition combined with OpenAI. They are going to have an absurd amount of data to optimize their models thanks to that, not sure how other AI focused companies can overcome that have to wonder at what point developers remember how anti-developer Microsoft used to be and potentially move away from their ecosystem. Credit t…

> have to wonder at what point developers remember how anti-developer Microsoft used to be Microsoft has historically been anti-opensource, but not anti-developer. Their first product was a BASIC interpreter and in my experience throughout the 90s and early 2000s their developer ecosystem (aka Visual Studio) has really been first-class. I am not a fan of Microsoft because they have been openly hostile to open source,…

the economic contracts offered to developers by Microsoft were very different than in other development ecosystems. Microsoft always represented a different economic culture than many others, developers chose their allies based on multiple criteria.

Re: GitHub Copilot X – Sign up for technical preview

#173

Post by airstrike »

mempko wrote: post #137
knodi123 wrote: post #118

Earlier quoted context omitted.

half our team is really entrenched with jetbrains. but aside from a couple of curmudgeons who are formally married to vim, I think VSCode and JetBrains has pretty much sewed up the market.

Listen, if I divorce vim, it will take half my stuff.

How about using vim mode in VS Code or is that like being in an open relationship?

Re: GitHub Copilot X – Sign up for technical preview

#174

Post by geraneum »

digdugdirk wrote: post #17
swader999 wrote: post #6

Earlier quoted context omitted.

One should expect both.

But since the question was asked about shareholders specifically, the guaranteed bottom line improvement is going to come from cutting labor and running leaner teams. That's where large corporations will go first.

That's the main idea behind developing such systems. It's telling execs: Hey, look, you are paying a lot of money to those pesky workers (i.e. developers) and we like that number. Give us a cut and we save you a lot of money. This is nothing new actually. Has happened over and over in other industries and is not really surprising. What happens is that a lot of added value that the developers were generating will be consolidated into the pockets of a few and the rest will be automated. They businesses cannot be upset about this because the ultimate goal of a business is not be your friend but to generate more money and one way is to reduce costs.

Re: GitHub Copilot X – Sign up for technical preview

#175

Post by cristiioan »

azemetre wrote: post #135

It doesn't say it in the blog post, but sign up to the preview does require a paid subscription to copilot. Unsure if this applies to those who are given copilot for free (doesn't apply to me as I pay).

I was able to apply with my student account(it has copilot and pro for free).

Re: GitHub Copilot X – Sign up for technical preview

#176

Post by knodi123 »

mikkelam wrote: post #3

I have absolutely loved copilot so far. I especially love how fast it handles indexing complex n-dimensional arrays, which I'm really bad at. I also feel like often pushes me to more formal solutions instead of hacking. I'd estimate a 10% velocity increase for me with it. Super excited for GPT-4 behind it.

My team was freaking out about copilot because we're conducting tech interviews right now, with a take home exam and some pairing sessions, and they're worried we'll hire a bonehead because he can make copilot spit out reasonable stuff in our contrived and simple interview scenarios.

But we finally had a guy whose take home test had tons of handling in the controller for cases we weren't even using, and test coverage of things that couldn't possibly fail, or were actually part of the core language and not our own code. It was really obvious! And when I wanted him to fix an SQL Injection problem in our pairing, copilot carefully preserved the bug while he was moving code around. Made me chuckle.

Re: GitHub Copilot X – Sign up for technical preview

#177

Post by RulerOf »

filmgirlcw wrote: post #119
w-m wrote: post #33

I tried getting myself on the CLI waitlist ( https://githubnext.com/projects/copilot-cli/ ). That they use ffmpeg as the example hits a huge pain point for me. But: "Next Waitlist by GitHub Next would like permission to: Act on your behalf Not owned or operated by GitHub" Why does signing up for a waitlist require me to give permissions to an app to act in my account? An app that isn't even officially from GitHub? Th…

It’s officially from GitHub. There is some weird language (that I’ll absolutely pass feedback on to the team), I think because GitHub Next is a different organization from GitHub proper, but I can assure you, this is an official GitHub app. But I totally agree that this isn’t a great/clear message about where this is from.

The domain name on that authorization prompt was more than enough to get me to decline.

I wouldn't have hesitated at all if it were at next.github.com.

Re: GitHub Copilot X – Sign up for technical preview

#179

Post by acedTrex »

efields wrote: post #96
mike_hearn wrote: post #71

Earlier quoted context omitted.

I hope that Copilot X will be brought to other IDEs as well, not just Visual Studio [Code].

The sublime plugin for Copilot works well enough already. I'm sure Copilot X will be something you can fold into any editor. I don't understand how so many folks seem to tolerate the UX lag in VSCode

VSCode never has any lag for me personally

Re: GitHub Copilot X – Sign up for technical preview

#180

Post by filmgirlcw »

RulerOf wrote: post #177
filmgirlcw wrote: post #119

Earlier quoted context omitted.

It’s officially from GitHub. There is some weird language (that I’ll absolutely pass feedback on to the team), I think because GitHub Next is a different organization from GitHub proper, but I can assure you, this is an official GitHub app. But I totally agree that this isn’t a great/clear message about where this is from.

The domain name on that authorization prompt was more than enough to get me to decline. I wouldn't have hesitated at all if it were at next.github.com.

Totally get it.

I’ve passed feedback on to the team so (hopefully) the CLI app will be be clearly from GitHub soon (we need to transfer it to the regular GitHub org and then there hopefully won’t be any confusion). GitHub Next exists in a different org from GitHub proper for lots of reasons, but we should definitely make it more clear that those experiments are still from GitHub.

Post reply on HN