5 ms·
> But that's what standard stand for. Except that standards still tend to get implemented differently, which is a massive shame. My life long dream is to devel
by jbrooksuk 14y ago
> But that's what standard stand for.
Except that standards still tend to get implemented differently, which is a massive shame. My life long dream is to develop once, deploy everywhere. We're getting there with libraries such as jQuery and Backbone.js however we're still a long way away from that whilst there are multiple browsers to contend with.
- rimantas 14y agoThats why folks at whatwg.org spent so much time trying to define how html should be parsed. Alas, that still does not fix the problem with different vendors implementing different parts of the same specification.
- yuchi 14y agoEvery vendor has its own needs and priorities. Would we be happy with a single implementation with incomplete support for a spec feature and no other implementation on the table? It's a possible scenario, in a WebKit only world. Don't get me wrong, I love WebKit, I love Chrome, but I also love Gecko AND Presto. They're doing a terrific work that must be rewarded.
- yuchi 14y agoWithout any aggressive intent, how could Backbone improve your cross-environment problems? It's just an MVC pattern implementation, it doesn't abstract you from nothing.
- dmnd 14y agoBackbone.Router working on non-pushState browsers is one example.