Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> So what is the conclusion? I have no idea how to fix our collective resource waste and it is hard to assign individual responsibility and I'm deeply dissatisfied by the whole situation.

I think the most likely conclusion is that once OSes are guaranteed to have a modern-enough browser engine (this is close to being true for Windows since they introduced WebView2), Electron could update their framework to use the system's native webview (or at least make it available as an option for the developer). This would bring back the problem of having to test in multiple browsers, but I'd rather test against an old version of Chromium, or even Safari, than have to test against the old Edge engine in WebView1.

Edit: Did some more reading, and the way Electron discusses WebView2 doesn't seem to imply that they're interested in integrating with it: https://www.electronjs.org/blog/webview2

But regardless, I think all it would take is someone else making a framework that uses native webviews and implements enough of Electron's APIs/tooling to be close to a drop-in replacement. (Then again, how many people are using Preact?)



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: