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

> Browser rendering engines are so powerful and versatile and universal I don't see how they can lose.

Well browsers are pretty damn heavy for an app that won't use 99% of its functionality. Maybe some of this can be amortized with clever distro work so apps don't have to ship the whole runtime but that hasn't happened yet.

(In fact, it's a little odd to me electron is based on chrome rather than the WebKit that actually ships with macos.... you should be able to ship that sort of app with a few megabytes)

I'd also rather eat glass than be stuck with javascript, easily the most frustrating ecosystem I've ever worked with by a very wide margin. Just the language is ok, but the build pipelines/bundling/transpilation/polyfillls is absolutely miserable to work with and lack of a decent standard library really hurts. It's crazy how we've basically lifted up the concepts of compilation and linking c objects to the world of javascript, just to ship code in a language the browser already fully supports.

Maybe WASM will help but my understanding its use of the DOM is quite awkward and still requires javascript usage.



How does WASM help with the concepts of compilation and linking c objects?




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

Search: