6 ms·
I think WebAssembly is one of the most exciting efforts for the web right now, second maybe only to Houdini or IPFS. I say that even as someone who works prett
by danShumway 9y ago
I think WebAssembly is one of the most exciting efforts for the web right now, second maybe only to Houdini or IPFS.
I say that even as someone who works pretty much exclusively in Javascript now and who loves the language - a lower level format will be great for everyone. I can't wait for more native languages to start supporting it.
- notheguyouthink 9y agoCan someone link Houdini that OP is referring to? I'm having trouble finding it without context due to the ambiguous name edit: is it this? https://github.com/w3c/css-houdini-drafts/wiki https://github.com/w3c/css-houdini-drafts/wiki
- laughingpine 9y agoYeah -- that should be the one they're talking about.
- danShumway 9y agoCorrect. Article talking about why Houdini is different from normal CSS polyfills: https://www.smashingmagazine.com/2016/03/houdini-maybe-the-most-exciting-development-in-css-youve-never-heard-of/ https://www.smashingmagazine.com/2016/03/houdini-maybe-the-m... And the related HN discussion (possibly a bit outdated): https://news.ycombinator.com/item?id=11357794 https://news.ycombinator.com/item?id=11357794
- xnaas 9y agoI haven't looked into IPFS in a long while. Is development going well? Has the userbase grown somewhat significantly in the past couple of years?
- haberman 9y agoI completely agree. I remember all the years where the prevailing wisdom was "standard web byte-code isn't necessary/feasible/desirable/etc." It's nice to realize that such pronouncements aren't necessarily the final word. It turns out there is a way to give people the byte-code they always wanted. (btw I know WebAssembly isn't, strictly speaking, byte-code. It's a compact binary encoding of an AST. But it has all the characteristics that people really cared about when they asked for byte-code: it's a low-level representation that is a good compilation target for compiled languages)
- dmix 9y agoIt might be a bit early to claim success though. We're still basically waiting for some mainstream well-regarded adoptions and use-cases. Not to say it's any less exciting in regards to it's potential. But it's important to keep expectations balanced by present outcomes.
- tyingq 9y agoThe wasm folks will add gc, polymorphic inline cache, dom interop, some time soon. That will enable things like browser side Perl, Python, Go, Ruby, etc, without having to push the whole runtime. Nonetheless, the bloat train will resume at that point. And, the frontend will start having the same amount of fragmentation as the backend. Good news for us, though, is job security. The resulting complexity helps us, at least in one way. Web apps will be on equal footing and fragmentation as the old client/server model (vb, powerbuilder, delphi, c/x11/motif, visual c++ / mfc, dart/flutter, etc). What comes around, goes around. The cyclic nature is pretty funny.
- jimmcslim 9y ago> And, the frontend will start having the same amount of fragmentation as the backend. Err, I think that boat has already sailed?... E.g. Grunt, Gulp, Webpack, make, Parcel, Brunch, Browserify, etc, etc, etc.
- 9y ago