4 ms·

> like requiring proprietary extensions to lock down the thing. Which they are already doing in a lot of places. For instance, the VSCode Python extension repl

> like requiring proprietary extensions to lock down the thing. Which they are already doing in a lot of places. For instance, the VSCode Python extension replaced the open source language server with a proprietary rewrite (PyLance)[0]. They also have quite a few extensions that are proprietary, like LiveView. And it's worth noting that those extensions explicitly forbid running in anything other than the official VSCode from Microsoft. Forks cannot legally run those extensions, and some of the extensions will have DRM to prevent it from happening[1]. [0]: https://www.reddit.com/r/Python/comments/n9yse1/as_of_today_updating_the_vs_code_python_extension/ https://www.reddit.com/r/Python/comments/n9yse1/as_of_today_... [1]: https://www.reddit.com/r/linux/comments/k0s8qw/vs_code_developers_prevent_running_the_new/ https://www.reddit.com/r/linux/comments/k0s8qw/vs_code_devel...

nonethewiser 4y ago
Which means it's not truly OSS. But I dont think its insidious for software to have good proprietary features that make the tool better.
- madeofpalk 4y ago
  It means that there is a truly OSS core VS Code (presumably what Gitlab and Code Sandbox uses), and proprietary extensions on top that Microsoft ship in their default (proprietary) distribution
  - Cthulhu_ 4y ago
    But given that the architecture is open source, there's nothing stopping the people behind e.g. Python from embracing the language server protocol and providing better tooling. Besides time / money, but that ties in to the known problem that open source is very difficult to monetize.
  - matkoniecz 4y ago
    If someone is a purist and wants to use it to avoid lock-in - it is available at https://github.com/VSCodium/vscodium https://github.com/VSCodium/vscodium
    - andrew_ 4y ago
      I gave this an earnest try over the course of a few months. There were notable bugs in nearly all of the extensions I needed to use for work. It's known that Microsoft ships custom builds of the open source portion of VS Code, and there's certainly something missing from the open source core. I ended up going back to hobbled Atom while I wait for projects like Zed to mature.
      - matkoniecz 4y ago
        And I am simply not using extensions. (Viable for me, may be not viable for others.)
      - lozenge 4y ago
        That doesn't make sense to me as there are next to no changes between VSCodium and VS Code. Unless these extensions were closed source Microsoft-authored?
        roblabla 4y ago
        > That doesn't make sense to me as there are next to no changes between VSCodium and VS Code. Honest question: How would we know that? Is it possible to somehow diff vscode's code with the open source repo? Is there an analysis available somewhere of the differences?
- yjftsjthsd-h 4y ago
  > But I dont think its insidious for software to have good proprietary features that make the tool better. Maybe not, but it's absolutely insidious to have open source features and then replace them with proprietary ones.

nonethewiser 4y ago

Which means it's not truly OSS. But I dont think its insidious for software to have good proprietary features that make the tool better.

madeofpalk 4y ago
It means that there is a truly OSS core VS Code (presumably what Gitlab and Code Sandbox uses), and proprietary extensions on top that Microsoft ship in their default (proprietary) distribution
- Cthulhu_ 4y ago
  But given that the architecture is open source, there's nothing stopping the people behind e.g. Python from embracing the language server protocol and providing better tooling. Besides time / money, but that ties in to the known problem that open source is very difficult to monetize.
- matkoniecz 4y ago
  If someone is a purist and wants to use it to avoid lock-in - it is available at https://github.com/VSCodium/vscodium https://github.com/VSCodium/vscodium
  - andrew_ 4y ago
    I gave this an earnest try over the course of a few months. There were notable bugs in nearly all of the extensions I needed to use for work. It's known that Microsoft ships custom builds of the open source portion of VS Code, and there's certainly something missing from the open source core. I ended up going back to hobbled Atom while I wait for projects like Zed to mature.
    - matkoniecz 4y ago
      And I am simply not using extensions. (Viable for me, may be not viable for others.)
    - lozenge 4y ago
      That doesn't make sense to me as there are next to no changes between VSCodium and VS Code. Unless these extensions were closed source Microsoft-authored?
      - roblabla 4y ago
        > That doesn't make sense to me as there are next to no changes between VSCodium and VS Code. Honest question: How would we know that? Is it possible to somehow diff vscode's code with the open source repo? Is there an analysis available somewhere of the differences?
yjftsjthsd-h 4y ago
> But I dont think its insidious for software to have good proprietary features that make the tool better. Maybe not, but it's absolutely insidious to have open source features and then replace them with proprietary ones.