Microsoft Teams 2 will use half the memory, dropping Electron for Edge Webview2

Re:Microsoft Teams 2 will use half the memory, dropping Elec... by failwhaleshark on Saturday June 26, 2021 @11:15AM (#27642581)

When and where it's a priority: creating a solid user-experience takes effort. If a project can't manage that when it matters, then their product or service is also going to suck in so many other ways their users will notice. Then native or not, it won't matter when everyone hates them.

Mac and iOS are relatively-straightforward, aren't terribly different, and share development resources.

Android (Kotlin) doesn't often lead to suicidal ideation.

Windows is meh.

Linux is so-so.

> So electron makes plenty of sense to developers

To mostly front-end developers who don't know much about the world outside of a browser.

> , even although it's an egregious resource hog.

Violating nonfunctional requirements to be usable, performant, and efficient.

[ Parent | on HN ]

Re:Microsoft Teams 2 will use half the memory, dropping Elec... by eloff on Saturday June 26, 2021 @04:13PM (#27645406)

> To mostly front-end developers who don't know much about the world outside of a browser.

Just for the record I'm a senior backend developer, who sometimes operates at CTO level in startups, and I suck at front-end development. But still electron makes sense to me. Or react native if it's mobile only.

The state of cross platform development is pretty bad.

[ Parent | on HN ]

Re:Microsoft Teams 2 will use half the memory, dropping Elec... by failwhaleshark on Saturday June 26, 2021 @05:21PM (#27646001)

It wasn't directed personally. The tendency is for front-end developers (the bulk of developers numerically) to treat software development like RMS does with emacs: everything extends from their perspective without consideration of perspectives or paradigms beyond their own. Embedded, native, real-time/mission-critical/fault-tolerance, resource-constrained, widely-compatible, ASIC/FPGA, and/or production-/shipping-scalable.

Cross-platform development will never be improved by N-times duplicated effort of abstraction layers on-top. The best that could happen is for OS developers to agree on common interfaces like UNIX/The Open Group for low-level operations, but for high-level media, UI, and common native development APIs more integrated than a patchwork of libraries like Qt, LibUV, etc.

I've worked on nuclear reactor simulators in F95, embedded industrial GPS equipment, deadline-oriented ad server meta-mediation, Fortune 500 client-facing consulting, compilers, functional programming projects, and now earn a paycheck doing SRE/PE since it's easy money to fund side-hustles.

[ Parent | on HN ]