3 ms·
No. His suggestion is to stop, and wait. Spend a year on standardizing, fixing bugs (like the bug with chrome where it sometimes just "forgets" float-css rule
by kuschku 11y ago
No.
His suggestion is to stop, and wait.
Spend a year on standardizing, fixing bugs (like the bug with chrome where it sometimes just "forgets" float-css rules), a year spent on improving issues and making everything behave consistently between browsers.
A year spent so that we won’t have to use jQuery afterwards anymore. Or underscore.js.
A year spent on fixing all the little bugs, and making a consistent roadmap where we actually want to go. Thinking about stuff like the Virtual-DOM of Angular or React and finding a better solution than that.
This is what we need to focus on. Making stuff behave consistently. And with one year, we can make sure that afterwards most of the market will actually use our new version. We can finally get rid of all the polyfills.
- bcg1 11y agoYou're missing my point. The world won't stop just because you decide to reflect on the situation and have small groups of people unilaterally decide what will someday maybe be standardized in some browsers. In the meantime the new features will get developed as non-standard features and you'll have even more proliferation of cruft, "polyfills" and whatever else PPK is complaining about.
- kuschku 11y agoWhy not? Why do we have to push new features every few weeks? The web still works right now, and it did in 2009, too.