[1] Time for a quick rant about HTTP/2 and WebAssembly.
-
-
Replying to @mikeal
[2] Somewhere along the way we decided that every problem we're going to have is fixed by either HTTP/2 or WebAssembly. This can't be true.
3 replies 11 retweets 11 likes -
Replying to @mikeal
[3] Pretty much every "big problem" people think these will fix, it won't.
2 replies 3 retweets 2 likes -
Replying to @mikeal
[4] We're still going to compile and bundle deps because without a better mechanism to share cache state the roundtrips are awful.
1 reply 4 retweets 4 likes -
Replying to @mikeal
[5] We are not going to have a multi-language web, JS will still be dominant, because the network and ecosystem effects will keep it there.
1 reply 5 retweets 7 likes -
Replying to @mikeal
[6] Don't get me wrong, HTTP/2 and WebAssembly will eventually transform how we do web development, but it'll take 5-10 years.
2 replies 8 retweets 10 likes -
Replying to @mikeal
[7] Anything 5-10 years out, we have no idea what that really looks like, and anyone trying to predict it will be wrong.
1 reply 2 retweets 8 likes -
Replying to @mikeal
[8] Two relevant technologies you can compare against: WebSockets and WebGL.
1 reply 1 retweet 4 likes -
Replying to @mikeal
[9] WebSockets has been around 5 years but we still can't rely on them and the way frameworks are built still hasn't adjusted.
2 replies 1 retweet 2 likes -
Replying to @mikeal
[10] WebGL since 2007, first time I saw a lib that took advantage of the underlying math speed w/o being compiled from C/C++ was last month.
2 replies 1 retweet 6 likes
a lot of the way that Flash slowly disappeared is these technologies. You're just not working on apps that care about them.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.