5 ms·

Does anyone know what makes VS Code an exception to this? Going to be working on an Electron app, so I'm curious about what optimizations have been made there.

52-6F-62 7y ago
I can't speak to VSCode, but I've been probably a hard use case for Electron development as I work in an industry without a ton of resources to throw at development, limited time, and less supportive environment for development (in spite of a pressing need to keep up). I've found keeping as precious little of the work in the render process as possible has helped a great deal. Send everything to the main process and use the event/messaging system to update the state. Then things that you're used to doing to maintain application performance in a web browser apply. Keep the compute in the back as much as possible. And depending on the task, offload compute to a native module [if you're capable and] if the expense between NodeJS <> native module is worth it (more intense compute tasks). There's probably more and more experienced advice out there, but this is my experience so far.
jayjader 7y ago
If I recall correctly, VS Code bundles its own Electron that Microsoft's team has spent considerable time & effort optimizing for it.
mdgrech23 7y ago
Pretty sure they forked electron. Not sure what they did to it. Also they probably drop down to native for a lot of tasks.
- Matthias247 7y ago
  No. They are even contributing to upstream Electron - and they did this before Github was acquired by Microsoft. They just run more efficient software on top of electron than others do.
armandososa 7y ago
Maybe something like: https://jlongster.com/secret-of-good-electron-apps https://jlongster.com/secret-of-good-electron-apps
kitsunesoba 7y ago
It’s likely just sheer difference in quality of engineering. For most companies that choose Electron, performance was never of any value in the first place and that’s reflected in the engineering regardless of how/what it’s written in. It just happens that bad code is much more egregiously bad with JS/Electron than with other stacks.

52-6F-62 7y ago

I can't speak to VSCode, but I've been probably a hard use case for Electron development as I work in an industry without a ton of resources to throw at development, limited time, and less supportive environment for development (in spite of a pressing need to keep up). I've found keeping as precious little of the work in the render process as possible has helped a great deal. Send everything to the main process and use the event/messaging system to update the state. Then things that you're used to doing to maintain application performance in a web browser apply. Keep the compute in the back as much as possible. And depending on the task, offload compute to a native module [if you're capable and] if the expense between NodeJS <> native module is worth it (more intense compute tasks). There's probably more and more experienced advice out there, but this is my experience so far.

jayjader 7y ago

If I recall correctly, VS Code bundles its own Electron that Microsoft's team has spent considerable time & effort optimizing for it.

mdgrech23 7y ago

Pretty sure they forked electron. Not sure what they did to it. Also they probably drop down to native for a lot of tasks.

Matthias247 7y ago
No. They are even contributing to upstream Electron - and they did this before Github was acquired by Microsoft. They just run more efficient software on top of electron than others do.

armandososa 7y ago

Maybe something like: https://jlongster.com/secret-of-good-electron-apps https://jlongster.com/secret-of-good-electron-apps

kitsunesoba 7y ago

It’s likely just sheer difference in quality of engineering. For most companies that choose Electron, performance was never of any value in the first place and that’s reflected in the engineering regardless of how/what it’s written in. It just happens that bad code is much more egregiously bad with JS/Electron than with other stacks.