News for hackers. Stuff that matters.
Re:Partial WebAssembly backend for the GNU toolchain by bitL on Saturday March 04, 2017 @06:52PM (#13793642)
It's more like you won't need to develop for two-three targets, like today with desktop, web and mobile. Instead you will use the same runtime, though there might be some restrictions on each platform you'd need to take into account (like handling permissions properly) and make sure your code would work on any platform that provides the capabilities you require.
Re:Partial WebAssembly backend for the GNU toolchain by Sanddancer on Saturday March 04, 2017 @07:05PM (#13793721)
Java promised that, but we got write-once, debug anywhere. Those different features, bugs, permissions, etc, mean you'll still have to test the platforms, build up different UIs for each platform, etc. About all you'd end up gaining is a stylesheet-based rendering engine, but you'd get that with something like XAML as well.
Re:Partial WebAssembly backend for the GNU toolchain by bobajeff on Saturday March 04, 2017 @07:31PM (#13793849)
Java doesn't support compiling C/C++ to their runtime. So that's not really comparable to this.
Re:Partial WebAssembly backend for the GNU toolchain by Sanddancer on Saturday March 04, 2017 @10:06PM (#13794360)
There is a currently dead project that does that https://github.com/davidar/lljvm . So I'd argue it is comparable.
Re:Partial WebAssembly backend for the GNU toolchain by bobajeff on Sunday March 05, 2017 @04:25AM (#13795207)
Like you said it's dead. Hypotheticals don't matter here only real tools we can use today.
Re:Partial WebAssembly backend for the GNU toolchain by johncolanduoni on Sunday March 05, 2017 @10:07AM (#13796235)
WebAssembly is much simpler than Java, and harder to get wrong. The DOM isn't, but I would hope non-web targets for WebAssembly would use different (and simpler) APIs.