Hacker News Reader

Note I said presentation logic, not application logic. Deciding when a button should grey out etc. is presentation logic. Its the kind of thing you fiddle with after you have your basic system done. I don't believe these minor look and feel stuff should be in the same boat as business application logic. Note you said fighting with content, presentation, and logic. In desktop apps MVC architectures are trivial to implement, no framework necessary. HTML JS are the things that are fighting you. In angular it doesn't. Complex presentation goes in directives (custom HTML tags! Woo! OO comes to HTML). Trivial boolean stuff can stay in the HTML. Business logic goes in the scoped controllers (woo, encapsulation made easy in JS).

i've been using ember for some time now for a complex application and everything seems to be clearly separated. Easily integrated with jqm and generally its model and controllers can be used effortlessly by other frameworks as well. Actually the complexity depends on the context and kind of integration.

Note I said presentation logic, not application logic. Deciding when a button should grey out etc. is presentation logic. Its the kind of thing you fiddle with after you have your basic system done. I don't believe these minor look and feel stuff should be in the same boat as real application logic.