4 ms·
That's an odd conclusion to reach: what drew me into Angular in the first place was it's extremely shallow learning curve. Going from nothing to prototype is ex
by debaserab2 12y ago
That's an odd conclusion to reach: what drew me into Angular in the first place was it's extremely shallow learning curve. Going from nothing to prototype is extremely fast, and if you mock your data correctly, can be leveraged into production code.
What eventually pushed me away from Angular is the performance of the scope digest cycle (which you won't even notice until you've built a large enough app to have a problem) and the odd state management issues that arise as a result of two way data binding.
- hippich 12y agoIt is all about where you draw a line. For example in my day job most projects require some form of dynamic loading parts of applications, which is VERY hard to do in proper way with angular. So if you need to make prototype with some fields auto updating some values somewhere - angular learning curve is probably fine. If you need to build complex and large UI - learning curve will be extremely painful.
- woah 12y agoWhat's your background? Did you do a lot of 'classic OOP' before picking up JS?
- debaserab2 12y agoNo, I've been programming javascript just as long as any server side language I've used that was OOP oriented.