IssueRaiser

>When you leave these behind, you have to think about scope hierarchies.

>When you leave these behind, you have to think about scope hierarchies. Yes, a prerequisite to using a JavaScript framework is understanding prototypical inheritance >You have to watch your watchers What? >I wish there was a simpler way for it to do its magic. To date I haven't seen a coherent argument against Angular; complaints seem focused around having to learn framework specific syntax (present in any large MVC framework) or the perceived "heaviness" of the framework (suggesting the apps you're building aren't complex enough to justify something like Angular)

Posted by cloakandswagger on Oct 14, 2014, 2:07 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.9,000 issues0 comments

complaint (Other)

>When you leave these behind, you have to think about scope hierarchies.

cloakandswaggerOct 14, 2014, 2:07 PM

>When you leave these behind, you have to think about scope hierarchies. Yes, a prerequisite to using a JavaScript framework is understanding prototypical inheritance >You have to watch your watchers What? >I wish there was a simpler way for it to do its magic. To date I haven't seen a coherent argument against Angular; complaints seem focused around having to learn framework specific syntax (present in any large MVC framework) or the perceived "heaviness" of the framework (suggesting the apps you're building aren't complex enough to justify something like Angular)

Comments (0)

No comments yet. Start the discussion.

Comment on this issue