3 ms·
On the web though, you don't need the user to manage libraries. In the same way you don't install a web page, libraries are simple script tags pointing at URLs.
by bastawhiz 10y ago
On the web though, you don't need the user to manage libraries. In the same way you don't install a web page, libraries are simple script tags pointing at URLs. Pages will never reference incompatible versions. Browser caching makes "sharing" of libraries transparent. What's there left to manage?
- zaphar 10y agoIs this still true for an application like VLC compiling to WebAssembly that uses other downstream libraries? What if VLC uses downstream libx and Audacity also uses downstream libx and downstream libx has a critical 0day. I'm not super clear yet on how the WebAssembly build pipelines works. Is dynamic linking done through script tags? or are the binary blobs statically compiled? I'm genuinely curious here how this is all supposed to work. How does one ensure that downstream libx is updated for all of the WebAssembly applications that use them.