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

I would ship a daemon/service that makes use of the user installed browser, if a Web interface must be.


And you would then be back to debugging small intricate differences across browsers, which is what people ship Electron to avoid.


Since I don't want to be part of Chrome marketing force, that is a very good thing to do.

Either go native or Web standards.


That's nice technically, but awful in terms of usability.


Only if the developer doesn't know any better.

It can replicate Electron UI/UX without the bloat or Chrome marketing.


Why?




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

Search: