3 ms·
> People wouldn't query the DOM if that wasn't the most effective way of getting stuff done. jQuery has a UI kit, it's called jQuery UI. And how is using jQuery
by Joeri 16y ago
> People wouldn't query the DOM if that wasn't the most effective way of getting stuff done. jQuery has a UI kit, it's called jQuery UI. And how is using jQuery equals to not using JavaScript to the fullest?
All UI toolkits leverage the DOM, that's not the point. The point is whether the DOM is at the appropriate level of abstraction for writing business app UI logic. I wrote at the level of the DOM for years, and when I switched to ExtJS it felt like a liberation. I spend way more time on business logic and experimenting with different UI designs, and far less time fighting with browsers.
> JavaScript is a prototypical language, you can't use it to the "fullest" if you force OOP on it.
OOP and prototypal inheritance don't conflict. You don't have to use classical inheritance to have a clean OO design.
- boucher 16y agoI think there are only a handful of people in the world who truly understand what building something on the level of complexity of a 280 Slides or GMail in jQuery really is. And I think even those people would agree that they'd be better off with a more structured framework, even if that was something built on top of / in conjunction with jQuery. In some ways I think that's where Backbone is trying to fit itself into the ecosystem. I think one of the fundamental realizations of building something complex that's fast and maintainable is that using the DOM as your source of application state is usually not the right way to do it.