3 ms·
Seems like the lesson should be extended to something like: Always test cross-browser before commiting to a js library, after you have committed to it, and on
by GrinningFool 9y ago
Seems like the lesson should be extended to something like:
Always test cross-browser before commiting to a js library, after you have committed to it, and on every browser or js library update.
- chiefalchemist 9y agoYes. But it also seems like the browser based model continues to be flaw. One application (i.e., browser) makes a single update and EVERYONE downstream now needs to retest? And Perhaps significantly refactor? This is a MAJOR UX violation. If you were going to by a car and you were told that's how it works you'd never buy that make/model. We keep getting by on the ignorance of end-user. That's not a positive. I'm not sure what the details of the answer is. But I do know that accepting the status quo is no longer acceptable. The first step to solving a problem is to admit you have one. Step 2 is to make sure you identify the right problem. We have a problem, yes?