Re:Electron 4.0.0
by InGodsName on Friday December 21, 2018 @11:44AM
(#18734488)
I think it's because VSCode uses typescript and it had better plugin architecture.
VSCode also uses lazy loading so doesn't initate everything at once you click the launcher icon but does it progressively.
Re:Electron 4.0.0
by fabiospampinato on Friday December 21, 2018 @11:55AM
(#18734567)
VS Code doesn't provide direct DOM access to extensions authors, that's definitely a deciding factor.
But a couple of years ago even simply writing inside Atom without using any extension felt sluggish to me.
TypeScript gets downcompiled to JavaScript anyway, so I don't think that's directly a contributing factor, but maybe because of the type system they can spend less time debugging and more time optimizing.
It's because much of the guts of VSCode is written in C++ and optimized.
Because, you know, Microsoft.
No it's not.
The file searching code is in Rust (IIRC) and runs as an external process, but that is about it.
Re:Electron 4.0.0
by InGodsName on Friday December 21, 2018 @01:31PM
(#18735376)
So eletrons lets you code part of it in C++?
Re:Electron 4.0.0
by fabiospampinato on Friday December 21, 2018 @02:06PM
(#18735664)
You can have native modules in Node.js, and you can use Node.js inside Electron.
I think most of the times if an Electron app is not snappy enough then the developers didn't spend enough time optimizing it, take a look at VS Code vs Atom for instance, I haven't used Atom in a while so maybe the situation in different now, but both are Electron apps, VS Code is fast and Atom is (was?) not.
[1] https://github.com/electron/electron/pull/14633