|
|
|
|
|
by croes
1845 days ago
|
|
You must view the browser with JS and WASM as a unit. The browser renders it's own GUI too, it's not OS native The browser uses lots of resources too. The browser is kind of a plugin to the OS and must be updated separately. Java nowadays is pretty fast too. Java VM serves a platform for multiple languages like Scala, Kotlin, Clojure. Let's face it, the browser is the new JVM and a soon it gets the same permissions like the JVM to access the file system and such, we get the same problems. |
|
> https://developer.mozilla.org/en-US/docs/Web/Security/Subres... : "Subresource Integrity (SRI) is a security feature that enables browsers to verify that resources they fetch (for example, from a CDN) are delivered without unexpected manipulation. It works by allowing you to provide a cryptographic hash that a fetched resource must match."
> There's a new Native Filesystem API: "The new Native File System API allows web apps to read or save changes directly to files and folders on the user's device." https://web.dev/native-file-system/
> We'll need a way to grant specific URLs specific, limited amounts of storage.
[...]
> https://github.com/deathbeds/jyve/issues/46 :
> Would [Micromamba] and conda-forge build a WASM architecture target?