5 ms·

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

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.

rvz 4y ago
> 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?
- mynameisvlad 4y ago
  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 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.
  - rvz 4y ago
    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
    - mynameisvlad 4y ago
      > 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-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide https://docs.github.com/en/copilot/getting-started-with-gith... https://docs.github.com/en/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim 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 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.
      - klibertp 4y ago
        > 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.
        mynameisvlad 4y ago

rvz 4y ago

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

mynameisvlad 4y ago
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 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.
- rvz 4y ago
  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
  - mynameisvlad 4y ago
    > 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-github-copilot/getting-started-with-github-copilot-in-a-jetbrains-ide https://docs.github.com/en/copilot/getting-started-with-gith... https://docs.github.com/en/copilot/getting-started-with-github-copilot/getting-started-with-github-copilot-in-neovim 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 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.
    - klibertp 4y ago
      > 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.
      - mynameisvlad 4y ago