News for hackers. Stuff that matters.
Re:GitHub Copilot X: The AI-powered developer experience by mike_hearn on Wednesday March 22, 2023 @10:36AM (#35261697)
I hope that Copilot X will be brought to other IDEs as well, not just Visual Studio [Code].
Re:GitHub Copilot X: The AI-powered developer experience by efields on Wednesday March 22, 2023 @10:45AM (#35261819)
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
Re:GitHub Copilot X: The AI-powered developer experience by joshmanders on Wednesday March 22, 2023 @10:49AM (#35261896)
> I don't understand how so many folks seem to tolerate the UX lag in VSCode

A lot of us don't experience any issues. To me, VSCode is just as performant as Sublime is.

Re:GitHub Copilot X: The AI-powered developer experience by eitland on Wednesday March 22, 2023 @11:54AM (#35263020)
I guess what you experience is how I experience 1 px misalignment and similar things that some people always complain about in KDE:

I don't notice it at all.

Modern software that doesn't react immediately even when running on even more modern hardware however, that grinds my gears.

Re:GitHub Copilot X: The AI-powered developer experience by acedTrex on Wednesday March 22, 2023 @11:06AM (#35262186)
VSCode never has any lag for me personally
Re:GitHub Copilot X: The AI-powered developer experience by epolanski on Wednesday March 22, 2023 @10:49AM (#35261885)
Maybe they have a better machine than you so they don't notice it.
Re:GitHub Copilot X: The AI-powered developer experience by jlkuester7 on Wednesday March 22, 2023 @11:15AM (#35262305)
My dev machine is sufficiently beefy (32G of RAM). I recently tried https://lapce.dev/ and was very surprised that it was noticeably more snappy than VSC. (I am not super sensitive to that kind of thing after years spent in Eclipse/IDEA.).

Made me realize how I can just become accustomed to a certain amount of lagging....

Re:GitHub Copilot X: The AI-powered developer experience by pzo on Wednesday March 22, 2023 @12:46PM (#35263759)
I recently tried lapce on my Mac and just empty editor with just one new tab was eating 70% of my CPU. I'd better IDE eat 1-2GB of ram than eat my CPU cycles. Also on their github lapce has more than 50% of open issues labeled as C-Bug - that's not very reassuring
Re:GitHub Copilot X: The AI-powered developer experience by crucialfelix on Wednesday March 22, 2023 @02:26PM (#35265162)
Try disabling all extensions.

I know there are startup metrics, and I would expect there are keystroke metrics to understand what's running

Re:GitHub Copilot X: The AI-powered developer experience by rvz on Wednesday March 22, 2023 @10:54AM (#35261998)
Here we go again with the editor lock in as precisely predicted. [0]

[0] https://news.ycombinator.com/item?id=27685104

Re:GitHub Copilot X: The AI-powered developer experience by mynameisvlad on Wednesday March 22, 2023 @11:17AM (#35262334)
I like how you probably spent more time looking up your multiple-year-old comment that could have instead been used to make sure that you’re not sounding like a fool that doesn’t know what he’s talking about.

They have already committed to releasing it to all editors Copilot supports. So, you know, the exact opposite of editor lock in.

Re:GitHub Copilot X: The AI-powered developer experience by rvz on Wednesday March 22, 2023 @11:55AM (#35263029)
> I like how you probably spent more time looking up your multiple-year-old comment that could have instead been used to make sure that you’re not sounding like a fool that doesn’t know what he’s talking about.

It took seconds and it is still true and evergreen to this day. Thanks for your so called 'concern'.

> They have already committed to releasing it to all editors Copilot supports. So, you know, the exact opposite of editor lock in.

They are more 'Committed' to supporting VS Code than giving total feature parity to other editors. Do you really believe everything that Microsoft / OpenAI feeds you?

Re:GitHub Copilot X: The AI-powered developer experience by mynameisvlad on Wednesday March 22, 2023 @11:57AM (#35263061)
Considering they have several third party editor logos in full display on their main landing page, I'm going to believe Microsoft and OpenAI over some random naysayer on the internet who didn't even bother to check.

https://github.com/features/preview/copilot-x

What benefit would they even gain from locking it to their free editor? If anything, VS Code is a way for Microsoft to push other services like Copilot. The strategy has been and continues to be to bring these services to where the developer is.

Re:GitHub Copilot X: The AI-powered developer experience by rvz on Wednesday March 22, 2023 @12:02PM (#35263136)
So there is 100% feature parity then for all other editors other than VS Code then? YES or NO?

As I said before, "They are more 'Committed' to supporting VS Code than giving total feature parity to other editors."

Sticking a bunch of logos with no guarantee of 100% feature parity as seen in VS Code is exactly what lock-in is.

> If anything, VS Code is a way for Microsoft to push other services like Copilot. The strategy has been and continues to be to bring these services to where the developer is.

Re-centralizing everything and owning the entire developer ecosystem to MS / GitHub. What could possibly go wrong? /s

Re:GitHub Copilot X: The AI-powered developer experience by mynameisvlad on Wednesday March 22, 2023 @12:52PM (#35263832)
> So there is 100% feature parity then for all other editors other than VS Code then? YES or NO?

Yes. If you had taken the time it took to look up your comment to actually do something productive like looking this up, you'd have probably found it yourself. Yet, here we are.

Copilot fully supports JetBrains and NeoVim alongside Code and VS:

https://docs.github.com/en/copilot/getting-started-with-gith...

https://docs.github.com/en/copilot/getting-started-with-gith...

In fact JetBrains is listed before VS proper in the getting started guides:

https://docs.github.com/en/copilot

Sounds totally like a place that "is more committed to supporting VS Code than giving total feature parity to other editors".

> Re-centralizing everything and owning the entire developer ecosystem to MS / GitHub. What could possibly go wrong? /s

How, exactly, is providing Jetbrains and Neovim support "re-centralizing everything"?

Next time, do the most bare minimum of research before you double then triple down on an absurd argument not based in reality.

Re:GitHub Copilot X: The AI-powered developer experience by klibertp on Wednesday March 22, 2023 @01:57PM (#35264745)
> How, exactly, is providing Jetbrains and Neovim support "re-centralizing everything"?

Bait and switch. If it's good enough that Neovim users can't live without it, pulling the plug from Neovim support will result in some subset of users converting to VS Code. Probably won't play out this way with Jetbrains, but editors with smaller following and nobody backing them will most likely suffer this fate. It's happening all the time, most notably with Google products. Google Talk that used XMPP was neat and I switched to it because I could use Pidgin to contact most of my contacts. Not only Google Talk stopped supporting the standard, it even died and was reborn as something else I think 3 or 4 times by now. Of course, my contacts stayed with Google, so I had to leave Pidgin behind. It's going to be similar here, though to what extent I'm not sure, maybe it won't be very noticeable, or maybe it will. We'll see.

Re:GitHub Copilot X: The AI-powered developer experience by mynameisvlad on Wednesday March 22, 2023 @02:31PM (#35265225)
That’s all fair, but that’s not even remotely what their argument was.

Their entire point is that Microsoft is re-centralizing everything by forcing people onto VS Code. Which is something they’re… just not doing.

This is also an optional, paid tool to help when coding. The comparison to Google Talk is IMO not relevant. It’s never going to be “good enough that someone won’t be able to live without it” because it’s at its core a completely optional tool.

If Copilot for NeoVim goes away in 5 years, you can just… stop using it. It’s not like we haven’t developed things without Copilot for decades now.

Re:GitHub Copilot X: The AI-powered developer experience by norman784 on Wednesday March 22, 2023 @10:59AM (#35262086)
Seems that you didn't bother checked their site before commenting. Check it out here[0], but TLDR: they have VS, VS code, Jetbrains and NeoVim logos in there.

[0] https://github.com/features/preview/copilot-x

Re:GitHub Copilot X: The AI-powered developer experience by celeritascelery on Wednesday March 22, 2023 @11:33AM (#35262643)
I don’t know about jetbrains, but the neovim plug-in is not full featured like the vscode one. For example, it doesn’t have the “explain this code” feature. The repo also does not allow issues or PR’s so you can’t even ask for it to have feature parity. I am a paying GitHub copilot user with the neovim plugin, but I find this second-class treatment frustrating. I expect copilot X to be more of the same, since it is even more deeply integrated into vscode.
Re:GitHub Copilot X: The AI-powered developer experience by Version467 on Wednesday March 22, 2023 @11:56AM (#35263042)
The page you linked only shows those logos in a block that specifically talks about Copilot, not Copilot X, so I don't see how this implies that Copilot X will come to those platforms as well.

(I expect implementations for those platforms to show up eventually, I just don't think the logos on that page are evidence for that.)

Re:GitHub Copilot X: The AI-powered developer experience by mike_hearn on Wednesday March 22, 2023 @12:38PM (#35263640)
The blog post we're talking about says specifically:

"We are bringing a chat interface to the editor that’s focused on developer scenarios and natively integrates with VS Code and Visual Studio."

Re:GitHub Copilot X: The AI-powered developer experience by highwaylights on Wednesday March 22, 2023 @11:01AM (#35262107)
They've already committed to bringing it to other platforms where Copilot is currently (JetBrains IDE's for example).
Re:GitHub Copilot X: The AI-powered developer experience by mwilsonthomas on Wednesday March 22, 2023 @03:30PM (#35266008)
Hey Mike: see this post for info about Copilot chat in Visual Studio 2022!

https://aka.ms/GHCopilotchatVS

Hope that helps

Cheers Mark Wilson-Thomas Program Manager, Copilot chat for Visual Studio

Re:GitHub Copilot X: The AI-powered developer experience by mike_hearn on Thursday March 23, 2023 @09:03AM (#35274074)
Hi Mark,

Thanks for the reply! Actually I was thinking of JetBrains IDEs, but I totally get why you're creating features for your own IDE line. If JetBrains want a similar feature, perhaps they'll have to build it themselves. Hopefully that actually is possible and OpenAI's stuff isn't now locked behind an exclusivity deal.