News for hackers. Stuff that matters.
Re:Responsive JavaScript in Rails: load what you need when y... by pothibo on Wednesday July 17, 2013 @11:11AM (#6058094)
I believe that what he meant (Correct me if I'm wrong), is that instead of creating a system of classes that tries to abstract everything out of the DOM, it's better act on the DOM itself, via jQuery, Zepto.js, etc.

In some ways, what I showed in the post is functional.

- Select a DOM i.e var $elem = $("#anElementId")

- Act on it i.e $elem.fadeOut()

Re:Responsive JavaScript in Rails: load what you need when y... by platz on Wednesday July 17, 2013 @11:28AM (#6058213)
And yet what about the "JQuery soup" problem that everyone complains about? Isn't that due to having DOM manipulation code strewn about willy-nilly?
Re:Responsive JavaScript in Rails: load what you need when y... by pothibo on Wednesday July 17, 2013 @11:35AM (#6058268)
Sometimes, it's good to encapsulate stuff into a class when you have a complex logic around a specific theme.

It's not one or the other. It's one AND the other.