Modern JS is a good language that's getting even better. It only sucks of because of the old quirks, that will never be fix because "we can't break the web". Why don't we fix it with new lang semantics, a new spec, and a compatibility mode flag to use the new JavaScript? 1/
-
Show this thread
-
We'll never move forward unless we abandon the sinking ship. Let's make the old code work on stagnant abandoned version of JavaScript engine, CSS and the DOM, and fork the existing specs to clean house. 2/
1 reply 0 retweets 14 likesShow this thread -
Sure, it'll take time to spec, implement and adopt. But as long as the old sites keep working, we can build a new foundation with better primitives. Build performance and features that the app and site implementers (and their money) want, and the browsers will follow.
2 replies 1 retweet 14 likesShow this thread -
In fact, this would be better for the "old web", since they would now have a stable immovable platform target they can keep their old unmaintained sites and their enterprise software working against. 4/
1 reply 0 retweets 8 likesShow this thread -
Meanwhile, new product implementers get to enjoy productivity and a better foundation, and web is able to compete with native. In the long term, we want the web to prosper, and in that long term all products and sites that matter will be on the new web 5/
1 reply 0 retweets 8 likesShow this thread -
Right now the browsers are able to do fantastic things, from VR to GL, and Bluetooth to Offline capability. Fantastic things. But it's all built on a heap of ~garbage~ history that's not making it productive to implement on, and only hampers the platform's eventual success 6/
1 reply 0 retweets 8 likesShow this thread -
Sure, it's going to be difficult. And expensive. And political. And unpopular. If it was easy, we'd have done it already. But you can't keep punting your technical debt forever to the next generation. The longer we wait, the harder it'll be. So why not? 8/8
2 replies 2 retweets 14 likesShow this thread
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.
JavaScript, HTML, CSS, HTTP, performance, security, Bash, Unicode, i18n, macOS.