3 ms·
It will be re-inventing the whole application containers ecosystems we had back a few decades ago across JVM and CLR ecosystems.
by pjmlp 2y ago
It will be re-inventing the whole application containers ecosystems we had back a few decades ago across JVM and CLR ecosystems.
- apitman 2y agoWhen you jump into every WASM thread with this take, what are you trying to accomplish?
- pjmlp 2y agoMake everyone aware, born after 2000's what is being re-invented, while being sold as innovative. You are free to ignore my comments.
- apitman 2y agoThat's a fair reason. It's important to realize how often we re-invent the wheel in our field. As an example, you're an expert in distributed systems, which I've only recently started dabbling in. In the process I'm learning how so many of the fancy "new" distributed systems and we have today were essentially invented decades ago. But in the WASM case, to what end? There's a cost to your comments. I'm sharing an example of how WASM has helped me solve a real problem, and might solve real problems for other people. Your comments create noise to these types of discussions. Maybe it's worth the tradeoff in your mind, but I'm curious what your end goal is?
- fc417fc802 2y agoI can't speak to his purpose but for myself I find it interesting to consider the differences that lead WASM to help you solve a real problem where the preexisting solutions presumably didn't.
- pie_flavor 2y agoWASM is designed to be embedded and its model is that of native code rather than any particular high-level language's primitives. It is closer to LLVM than Java. Comparisons to Java are surface-level and boring, since all foundational reasons why Java failed are false of WASM.
- pjmlp 2y agoInterestingly enough, people keep forgetting that since UNCOL in 1958 there were many polyglot bytecode based runtimes, because comparing to Java is always easier argument.
- pie_flavor 2y agoYou're the one who brought it up. Make a good point or don't.
- panick21_ 2y agoBelieve it or not, just because on an abstract technically something similar has been done before, its possible for people to still care about something that is being built. Reinventing the wheel is perfectly fine and even good, special if it happens in a different context and with a different community and process. And the WebAssembly people are well aware that Java/CLI exist and are learning from it. Making the same comment on every single Webassembly thread for the last couple years as if the everybody working on WebAssembly or WASI is some bro-programer born in 2008 is just disrespectful to the engineers working on these projects. Sorry that we are not all as cool as you and use UNCOL everyday. I mean who would want to use a technical idea that isn't first of its kind.
- tadfisher 2y agoSeems to have a lot more momentum though? I can run Haskell on WASM, and all the backends for JVM and CLR are long dead. More to the point, I can target the browser without plugins, lock-in, or security problems.
- pjmlp 2y agoAnd in a couple of years the same will most likely happen to the WASM backend. That was already possible with Haskell to JavaScript.
- pie_flavor 2y agoFor all browser targets to die, people must no longer be interested in writing Haskell while writing webapps, even though people will probably remain interested in writing Haskell, and probably remain writing webapps, which seems unlikely. For the WASM target to die and the JS target to remain, this would have to mean that there is some technical barrier that makes the maintenance burden not worth the staggering performance gain, and if there is some such burden I am not aware of it. 'Java died so WASM will die because both are VMs' is basically a content-free dismissal - what do you actually think will no longer be needed, or is currently not needed but overvalued, and why?
- pjmlp 2y agoYet we are talking about targeting the server in this thread, because so far the tooling for the browser sucks, and VCs are more willing to sponsor startups selling server products. Java not only is pretty much alive on the server, so is .NET, Erlang, and plenty of compiled languages that have always been a better alternative to JavaScript.
- pie_flavor 2y agoI am comparing your words about WASM to your words about JS. Misdirections about VCs are irrelevant. You can expect the WASM target to have as great or greater longevity than the JS target, and if your prediction about future failure isn't true of JS then it won't be true of WASM.