Re:Go gets preliminary WebAssembly support
by jayd16 on Saturday April 14, 2018 @02:50AM
(#16836235)
Hmm, maybe language runetimes can be dynamically linked and hosted by the language maintainers. Everyone imports the official library so the odds of the user already having most of everything cached is high.
[ Parent
| on HN ]
Re:Go gets preliminary WebAssembly support
by hawski on Saturday April 14, 2018 @03:05AM
(#16836271)
Aren't cache gained savings a myth? Browsers have cache in magnitude of tens of megabytes and most sites have different versions of everything.
Re:Go gets preliminary WebAssembly support
by netheril96 on Saturday April 14, 2018 @05:35AM
(#16836637)
Well, subresource integrity was not a thing before.
Re:Go gets preliminary WebAssembly support
by oelmekki on Saturday April 14, 2018 @04:40AM
(#16836513)
This would be cool: shared objects over internet. Interesting direction to explore.
Oberon, Java, Limbo, .NET, Flash, ActiveX already explored it.
Re:Go gets preliminary WebAssembly support
by jayd16 on Saturday April 14, 2018 @12:38PM
(#16838076)
if we were satisfied with that answer we wouldn't be talking about wasm at all.
It all boils down to politics.
Flash bad, Flash compiled to wasm, good.
AppFS (http://AppFS.rkeene.org/) supports this