[toyg]

The irony of talking about "regular people" and then using Slack as somebody "regular people" actually use.

"Regular people" are likely to encounter electron by using Telegram or Whatsapp on the desktop, or some recent MS product like Skype. Whether they care or not about bloat, I don't know. I know those chat programs used to have annoying problems with cut & paste and not supporting basic assistive technology (i.e. the "emoji keyboard"), but I have to admit they got better with time; if those fixes have made it upstream to Electron, then things are improving. They are still horribly opaque to native OS services like sharing facilities and whatnot, but it looks like OS developers themselves are throwing all that away these days, so...

I expect the real issue Electron might never solve is real support for more advanced assistive tech for the visually-impaired and other disabled people. That stuff barely works with traditional desktop tech as it is. Obviously that has never been an obstacle in the market at large, it mostly plays a part in public-procurement processes.

[AnIdiotOnTheNet]

As usual, "regular people" means whatever the poster needs it to mean in order for their argument to make sense. It's a straw man.

[sorenjan]

> "Regular people" are likely to encounter electron by using Telegram or Whatsapp on the desktop

Telegram is written in C++ and uses Qt. Maybe you're thinking of Discord?

https://github.com/telegramdesktop/tdesktop

[FiddlyPack]

Electron has a leg up in this regard long term, insomuch as the web is a platform that folks using assistive tech often use, Chromium is a reasonable target for assistive web technologies, and Electron apps have a higher chance of using accessible semantic building blocks by default.

Now, in practice? Yeah, not so good right now.

[chupasaurus]

Telegram Desktop is a Qt-based app and it doesn't run everything on top of QtWebEngine.