4 ms·
I looked at Angular a while ago in comparison to Knockout. Angular strikes me as one of those frameworks that requires you to get to a certain mental state in
by matt_s 13y ago
I looked at Angular a while ago in comparison to Knockout.
Angular strikes me as one of those frameworks that requires you to get to a certain mental state in order for you to use it. Maybe it just requires an extensive project being built to really appreciate it.
For someone doing web development on a casual basis there is too much meta and magic under the hood with Angular. When you have to quickly get up to speed on something you (or someone else) wrote but haven't touched in days or weeks then I'd prefer not have to do mental gymnastics before getting stuff done.
I'd prefer KISS and obvious solutions.
- Quarrelsome 13y agoYou're missing out. All it forces you to do is push your html fiddling into directives and use dependency injection (which is awesome anyway). It does way more than knockout.
- mcv 13y agoIt's important to realize that Angular is not simply a library, it's a framework. It starts up your app for you based of stuff you declared somewhere, and then it calls your code when your code is needed. It's actually quite comparable to frameworks like Spring, Wicket, Grails, Rails etc. The magic under the hood is not significantly different from the magic of those frameworks. It presents you with an environment to work in, rather than only doing what you tell it to. That environment can be limiting in some ways, but it also handles a lot of boring stuff for you. You need to learn how to work in that framework, but once you do, you're up to speed much faster.