- cross-posted to:
- hackernews@lemmy.smeargle.fans
- cross-posted to:
- hackernews@lemmy.smeargle.fans
Finally, another web engine is being developed to compete with Chromium and Firefox (Gecko), and they’re also working on a browser that will use it.
Finally, another web engine is being developed to compete with Chromium and Firefox (Gecko), and they’re also working on a browser that will use it.
It just makes too much sense… The only way to get past electron is a better electron. Or just fix electron
We’ve been going after this concept for decades now. That’s what java swing was supposed to be, what python gtlk was supposed to be, and I’m sure there were others before that and there’s been a hell of a lot since then
It’s all trade-offs between flexibility, ease of use, and performance. Also between maintenance cost, portability, and existing library support
Electron is a good compromise. The execution could be better, but it’s come a long way. There is no one size fits all solution, but there are some decent options that handle that compromise differently