Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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



> 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.


> 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.


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.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: