teleclimber
Joined 13 years ago
Joined 13 years ago
https://www.w3.org/community/httpslocal/ https://httpslocal.github.io/proposals/ https://httpslocal.github.io/usecases/
I wish some of this work would continue as well.
- https://github.com/w3c/ServiceWorker/issues/745 - https://github.com/w3c/geolocation-sensor/issues/22
There is another factor you may not be aware of: shopping apps are juicy targets for acquisition by marketing/data mining company. I mean, there is no clearer indication of what you want to buy than what you put in your shopping list, so it's perfect source of data to mine.
Out of milk is such an example: it was a good app with 5 million users, then it got sold. Users became the subjects of data mining, or their account got deleted (if in Europe). Fun!
https://www.prnewswire.com/news-releases/inmarket-acquires-o...
https://twitter.com/JamesLiamCook/status/1407370148349198341
* fictional quote but it wouldn't shock me if it became real
I don't think Firecracker's existence makes WASM's isolation uninteresting. First, I think you are looking at way more resources running a full VM (even a "micro" VM) compared to a WASM runtime. I think startup times are not comparable either, so if that matters you'll find WASM to be the way to go.
Second, WASM's capability-based security model is wonderful for giving the untrusted code the things it needs to work with. With a VM, you have to stitch together with shared directories, virtual eth bridges or, linux capabilities, maybe some cgroups, and who knows what else. (Granted you may need to do some of that with WASM too, but less so).
Kenton Varda did a pretty great writeup on CF worker security [0]. Would love to see Deno Deploy do something similar.
[0] https://blog.cloudflare.com/mitigating-spectre-and-other-sec...
I love the promise of WASM, but every time I look at it I get lost in a sea of acronyms, and my optimistic ideas of using language X with library Y on runtime Z are dashed because there is some missing piece somewhere.
If anything, the "any language" thing creates a giant matrix of potential pitfalls for the programmer.
In comparison, the combination of JS/TS, the browser API and a solid std lib looks pretty good for some problems.
https://abcnews.go.com/US/mysterious-bmw-fires-continue-call...
Currently building Dropserver. https://dropserver.org/