4 ms·
That is really awesome. But OP and parent talk about Microsoft Teams.
by jansan 4y ago
That is really awesome. But OP and parent talk about Microsoft Teams.
- c54 4y agoBoth are electron apps. I think the parent poster meant just to say "Here's an example of an Electron app that's quick, I'm not sure that Electron itself is the issue"
- Entinel 4y agoThey said Electron apps. The person is just noting that not all Electron apps run like garbage.
- cephei 4y agoI believe the relevance comes from the fact that both are built on Electron.
- sokoloff 4y agoVSCode uses Electron, making it entirely relevant to this thread.
- deleted 4y ago[deleted]
- explaininjs 4y agoOP talks about Electron, which vscode uses. The issue is in the application architecture, not the platform architecture. VSCode uses raw TS with no frameworks and all handcrafted events (manually attaching and detaching dom event listeners is commonplace, and hand wiring each event’s propagation chain is as well), Teams hops to the current flavor of the week framework when they get too far up a tree with the last rewrite’s. VSCode has also never been rewritten from the ground up, whereas this is Teams’ fourth or fifth time by my count. VSCode also has about 50 people on it, all said and done (PM, Design, etc included), teams has well over a thousand. It’s really quite an interesting case study. The lesson being, IMO: stop worrying about electron vs native vs angular vs rust vs react vs blah blah blah and just: - don’t be afraid to write good code - profile often
- Fell 4y agoAnd yet, VSCode cannot render at 60 FPS on my 2013 laptop. Any other program does. I don't expect Teams to perform better. Electron is a waste of resources. A high price to pay for the convenience of easy multiplatform applications.