Web Assembly now supported across all browsers

Re:Web Assembly now supported across all browsers by pjmlp on Monday December 04, 2017 @08:37AM (#15843649)

Not having a GC is just an implementation detail.

Anyone can implement one and ship it with the statically compiled WASM code, it is no different than targeting an actual machine code, unless we are speaking of CPUs like Intel iAPX 432.

The only issue is having a little bigger download, which is irrelevant in the age where web pages to display static text are bigger than the whole Quake installation.

[ Parent | on HN ]

Re:Web Assembly now supported across all browsers by banachtarski on Monday December 04, 2017 @01:03PM (#15845964)

Yes I'm aware. It's a side-consequence that I just happened to single out. GC is opt-in, not mandatory.

As for the bigger download, I'm hoping we'll be able to load libraries dynamically through WASM so you can cache things like the C runtime separately

[ Parent | on HN ]

Re:Web Assembly now supported across all browsers by pjmlp on Monday December 04, 2017 @02:15PM (#15846567)

Ah ok, sorry I thought it was another kind of remark relating GC just because the interoperability with JavaScript's GC is not yet baked into WASM.

The idea of caching runtimes looks good, but we need some kind of versioning, otherwise it will be yet another WASM.so hell.

Maybe tying them to the origin would be a possible solution.

[ Parent | on HN ]