[tomcatfish]

Everyone saying "This isn't a speedup, this is VSCode stopping being dumb" hasn't read carefully enough:

The speedup is from taking extension code built on a limited API and implementing it inside VSCode, using more information while doing so.

[bluSCALE4]

I read it as extension developers will never be able to match core since their api is limited.

[mynameisvlad]

I mean, yes? That's kind of the point of extensions; to provide additional functionality through specific APIs.

Chrome/Safari/Firefox extensions certainly don't have full access to everything the browser can do. Nor can IntelliJ plugins. Nor can... practically any other implementation of extensions.

https://github.com/microsoft/vscode is available if a developer wanted to contribute something to core, anyway.

[taeric]

Emacs stands in stark contrast to this claim, though. Some things do get moved into native code so that it can run faster, but at large most of it is implemented in the same code and paths that everyone has access to at runtime.

(For examples of "to run faster," I'm talking of json and such. Calling out to the tree-sitter library is there, too. I'm not clear why that has to be native, oddly.)

I can certainly understand and agree with browsers having more locked down sections. For expert developer tools, though, it does feel a touch weirder.