things like HTTP/2 and WebAssembly are like raw putty. They're genuinely new capabilities but take time to mold.
-
-
Replying to @wycats
not just time to implement and mold, but time for people to even realize what is possible once you can take them for granted
2 replies 1 retweet 3 likes -
You're both right ofc but I hasten to add we could have gone faster. WebGL from OpenGL-ES, and lagged. asm.js was fall 2012.
1 reply 1 retweet 4 likes -
I re-read a silly HN thread on Dart; not gonna rehash. Too much time lost while raw h/w & unsafe-native advanced as they do.
1 reply 0 retweets 1 like -
Replying to @BrendanEich @mikeal
it's hard to say we could have gone faster. Time to penetrate is non-zero; nex-gen builds on prev-gen.
1 reply 0 retweets 0 likes -
No, it's easy (HN link: https://news.ycombinator.com/item?id=9198888 ). Major time misspent in last 10 yrs on prop. agendas, cost 3 years minimum.
1 reply 0 retweets 3 likes -
Replying to @BrendanEich @mikeal
sure, but we have to accept that consensus means consensus with misguided people, and consensus wins.
1 reply 0 retweets 0 likes -
Those not in consensus, beneficiaries of boondoggle funding, weren't even in the room with us till the bleeding obvious won.
1 reply 1 retweet 1 like -
Replying to @BrendanEich @mikeal
but at least the bleeding obvious can still win!
1 reply 0 retweets 1 like -
That is not obvious from studying history. By the time the last-round winners misspend and capitulate, the game has changed.
1 reply 0 retweets 1 like
I just meant it happened this time. And maybe people are wising up.
-
-
Maybe. "Next time will be different" sometimes is right. Smartphone so much different & bigger than PC in Bell's Law sense.
0 replies 0 retweets 5 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.