4 ms·

So, the answer to your headline of why batman.js over AngularJS is because of "invalid html" attributes despite that being incorrect? If you just vetoed Angula

So, the answer to your headline of why batman.js over AngularJS is because of "invalid html" attributes despite that being incorrect? If you just vetoed AngularJS based on an incorrect assumption, why would it be your summary headline? How even did those attributes impact your system and force you to explore alternatives? I'd suggest a less sensationalist headline: "SUSE Studio uses Batman.js because due to familiarity and ease of rails integration".

vlad 14y ago
Even though the author updated the article to point out that Angular definitely works with strict HTML, he or she left the conclusion that AngularJS requires "invalid" HTML to use it to full capacity. That's incorrect.
- taproot 14y ago
  Aside from the poor title choice, I find it hard to discount that angular encourages invalid html. Work arounds aside, it says a lot about the framework mentality. I should probably note that in general I dislike the ideas put forward by angular, knockout, and similar. Binding logic to your view or in other words tight model/view coupling is just a stupid idea in the first place, it is quite plainly analogous to inline scripting like binding click events with onclick albeit in a slightly tidier way. These frameworks basically undo the last decade or so of separating logic from presentation. Feel free to discount / argue my point, I'm interested in a response as it is an opinion more than anything else. I have seen these frameworks work well, I just don't really agree with the ideas.
  - kevinastone 14y ago
    Thanks, I wanted that little expansion about the concerns about Angular's markup. I, in fact, think quite the opposite and appreciate(d) both Knockout and AngularJS's data binding models to make it much easier to create more interactive web apps without the usual boilerplate of DOM manipulation (or other scaffolding) required in other frameworks.

vlad 14y ago

Even though the author updated the article to point out that Angular definitely works with strict HTML, he or she left the conclusion that AngularJS requires "invalid" HTML to use it to full capacity. That's incorrect.

taproot 14y ago
Aside from the poor title choice, I find it hard to discount that angular encourages invalid html. Work arounds aside, it says a lot about the framework mentality. I should probably note that in general I dislike the ideas put forward by angular, knockout, and similar. Binding logic to your view or in other words tight model/view coupling is just a stupid idea in the first place, it is quite plainly analogous to inline scripting like binding click events with onclick albeit in a slightly tidier way. These frameworks basically undo the last decade or so of separating logic from presentation. Feel free to discount / argue my point, I'm interested in a response as it is an opinion more than anything else. I have seen these frameworks work well, I just don't really agree with the ideas.
- kevinastone 14y ago
  Thanks, I wanted that little expansion about the concerns about Angular's markup. I, in fact, think quite the opposite and appreciate(d) both Knockout and AngularJS's data binding models to make it much easier to create more interactive web apps without the usual boilerplate of DOM manipulation (or other scaffolding) required in other frameworks.