4 ms·

Maybe someone should just fork VS Code in a more liberal way, then everyone can build their extensions on top of that.

• johnfn 1y ago
  The restrictive extension ecosystem was a big part of VSCode's success. You can compare to Atom, which allowed extensions to do whatever they wanted: Atom ended up feeling exceptionally slow and bloated because extensions had full latitude to grind your IDE to a halt.
  • stevage 1y ago
    Yeah, I don't have a problem with that! But since there seems to be a need for AI-powered forks of VS Code, it could make sense for them all to build off the same fork, rather than making their own.
    • johnfn 1y ago
      Isn’t that what they’re doing by building off of vscode?
      • mp5 1y ago
        Yup, just rebased about a week ago
• sureIy 1y ago
  Ask Firefox how that went. Hint: they dropped XUL because every update broke extensions
  • stevage 1y ago
    That's not comparable though, right? I'm suggesting a third party forks the main product.
    • sureIy 1y ago
      Worse. The result is the same: an unmaintainable product, and now you also become increasingly incompatible with the source.