4 ms·

Wow, this include VS Code https://flathub.org/apps/com.visualstudio.code https://flathub.org/apps/com.visualstudio.code

pojntfx 2y ago
Yeah, Microsoft doesn't really support Flatpak. VSCodium is verified though and there isn't really any reason to use the proprietary VSCode anymore these days: https://flathub.org/apps/com.vscodium.codium https://flathub.org/apps/com.vscodium.codium
- resoluteteeth 2y ago
  > there isn't really any reason to use the proprietary VSCode anymore these days There is if you want to use some of Microsoft's extensions legally
  - somerandomqaguy 2y ago
    Do you know if there an easy way to identify which extensions are tied into VSCode itself vs a third party build? Or is it just install and try?
  - undefined9059 2y ago
    legally. lol. You are not allowed to ship the extensions outside of Microsofts control. But nothing stops you from downloading the extension from the marketplace and installing them manually. Or just use the registry anyway. Who's gonna check it?
Kalanos 2y ago
VSCodium is verified though https://flathub.org/apps/com.vscodium.codium https://flathub.org/apps/com.vscodium.codium
- mort96 2y ago
  I wish VSCodium was a viable alternative, but the sheer amount of unsupported first party plug-ins makes it a no-go. License issues prevents the C and C++ integration from working, remote editing is a halfway working unsupported hack which breaks with editor upgrades. At least that was my experience when I tried to switch to a "modern" GUI editor. In the end I just stuck with neovim; it seems more reliable and has better working C/C++ integration and remote editing.
  - elashri 2y ago
    The C/C++ extension is open source with MIT license but the shipped extension binary contains MS proprietary binaries that is not as open [1]. I am not sure what will be the difference between using MS official build and compiling the source (there will be some for sure). [1] https://github.com/microsoft/vscode-cpptools/blob/main/LICENSE.md https://github.com/microsoft/vscode-cpptools/blob/main/LICEN...
  - arcanemachiner 2y ago
    Same. Not being able to use the SSH plugin made VSCode DOA for me when I tried it a while back.

Yeah, Microsoft doesn't really support Flatpak. VSCodium is verified though and there isn't really any reason to use the proprietary VSCode anymore these days: https://flathub.org/apps/com.vscodium.codium https://flathub.org/apps/com.vscodium.codium

resoluteteeth 2y ago
> there isn't really any reason to use the proprietary VSCode anymore these days There is if you want to use some of Microsoft's extensions legally
- somerandomqaguy 2y ago
  Do you know if there an easy way to identify which extensions are tied into VSCode itself vs a third party build? Or is it just install and try?
- undefined9059 2y ago
  legally. lol. You are not allowed to ship the extensions outside of Microsofts control. But nothing stops you from downloading the extension from the marketplace and installing them manually. Or just use the registry anyway. Who's gonna check it?

Kalanos 2y ago

VSCodium is verified though https://flathub.org/apps/com.vscodium.codium https://flathub.org/apps/com.vscodium.codium

mort96 2y ago
I wish VSCodium was a viable alternative, but the sheer amount of unsupported first party plug-ins makes it a no-go. License issues prevents the C and C++ integration from working, remote editing is a halfway working unsupported hack which breaks with editor upgrades. At least that was my experience when I tried to switch to a "modern" GUI editor. In the end I just stuck with neovim; it seems more reliable and has better working C/C++ integration and remote editing.
- elashri 2y ago
  The C/C++ extension is open source with MIT license but the shipped extension binary contains MS proprietary binaries that is not as open [1]. I am not sure what will be the difference between using MS official build and compiling the source (there will be some for sure). [1] https://github.com/microsoft/vscode-cpptools/blob/main/LICENSE.md https://github.com/microsoft/vscode-cpptools/blob/main/LICEN...
- arcanemachiner 2y ago
  Same. Not being able to use the SSH plugin made VSCode DOA for me when I tried it a while back.