3 ms·

If I need VS Code, I reach for VSCodium. https://vscodium.com/ https://vscodium.com/

• nitinreddy88 2y ago
  You didn't even read the article. Did you? How vscodium solves the problem of author?
  • RunSet 2y ago
    > Ultimately, it comes down to this: Flatpaks run isolated from the host OS, which is fundamentally incompatible with developing code in an IDE. I consider vscodium to solve that problem by integrating with the operating system. https://vscodium.com/#use-a-package-manager-deb-rpm-provided-by-vscodium-related-repos https://vscodium.com/#use-a-package-manager-deb-rpm-provided...
    • davidt84 2y ago
      VSCode provides packages too. The problem is the OS defaulting to a flatpak.
      • RunSet 2y ago
        I credited the article's author with being able to summarize their problem. Since Fedora 39 does not default to a flatpak in the case of VScodium, it also solves the problem you describe.
• Waterluvian 2y ago
  Is there a complete listing somewhere of exactly what’s different between the two, both in terms of features and end-to-end experience?
  • dagw 2y ago
    The core program is exactly the same, built from the same source code, using the same build script, just with different default settings and configs (mainly turning off all telemetry and changing the branding). The big difference is when it comes to extensions. VSCodium does not have access to the official Microsoft extension marketplace or any of the closed source Microsoft extensions. Most Open Source and third party extensions are available, but a few will be missing, with the biggest one probably being the Remote Development tools.
• lc64 2y ago
  It's not the topic of the article.