News for hackers. Stuff that matters.

A comment on Mozilla announces WebAssembly System Interface, what JVM should have been. Parent comment

Re:Mozilla announces WebAssembly System Interface, what JVM ... by nwah1 on Monday April 22, 2019 @04:14AM (#19717324)
I agree largely from a development perspective, but the client-side javascript frameworks are ultimately more performant, particularly on mobile, and are not as bad as they used to be. Neither server-side nor WASM are ideal for mobile devices. Downloading many megabytes of .NET dependencies for a WASM app is obscene compared to like 30 kilobytes for React.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by manigandham on Monday April 22, 2019 @03:30PM (#19722036)
It won't be megabytes, that's only in the experimental phase. Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs.

As far as performant, I agree it wont matter in most trivial interactions but large datasets with computations already see an impact (for example we have million row datatables to show sometimes).

[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by TimTheTinker on Monday April 22, 2019 @03:43PM (#19722151)
> Binaries can shrink dramatically once run through a linker and trimmed down to only used APIs.

It's worth pointing out that .NET Core has an assembly/executable generator that can package only the .NET libraries that are actually used.

[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by nwah1 on Tuesday April 23, 2019 @11:42AM (#19729680)
Rust-based WASM front-end libraries will likely be small and also high performance. Unfortunately, all of the existing ones are highly experimental right now.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by davidhyde on Monday April 22, 2019 @06:09AM (#19717702)
> “30 kilobytes for React” This is just not even close to being true.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by nwah1 on Monday April 22, 2019 @10:18AM (#19719098)
The compressed size is 31 kb, and other frameworks are smaller.

https://gist.github.com/Restuta/cda69e50a853aa64912d

[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by namelosw on Monday April 22, 2019 @07:26AM (#19718017)
There's 3kb Preact with almost identical API.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by StavrosK on Monday April 22, 2019 @08:01AM (#19718188)
So what's the other 27KB+ for?
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by dmitriid on Monday April 22, 2019 @08:17AM (#19718297)
Fiber, support fo async rendering, suspense, hooks. A different VDOM algorithm.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by tracker1 on Monday April 22, 2019 @07:28PM (#19724102)
Better error handling and messaging...
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by thefounder on Monday April 22, 2019 @04:36AM (#19717401)
With 5g that won't be an issue anymore...
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by quantummkv on Monday April 22, 2019 @07:06AM (#19717923)
Until they decide that 5g is good enough to allow them to ship the browser with every website. Net speeds have been increasing every year and yet the websites take longer to load.
[ Parent | on HN ]
Re:Mozilla announces WebAssembly System Interface, what JVM ... by sdfsdfsdfsdf3 on Monday April 22, 2019 @06:54AM (#19717873)
In 2026 maybe...
[ Parent | on HN ]