4 ms·

Factors in Angular's success: * backed by Google * MEAN * plenty of media/blog coverage * seductive examples (that don't reflect best practices) My personal g

by pluma 12y ago

Factors in Angular's success: * backed by Google * MEAN * plenty of media/blog coverage * seductive examples (that don't reflect best practices) My personal gripe is with the last point. A lot of the appeal is in the two-way binding -- which is often the first thing to go out of the window once scaling becomes a problem. Also, I have no idea why the author thinks Browserify and Angular go well together. They don't. At all. Browserify is great on its own, but there's not really any "blessed" way of using a module system with Angular (and like jQuery Angular 1.x is tightly coupled with the global scope).

mk3 12y ago
Regarding seductive examples. I recently found out, that most of the examples even example apps are lacking best practices, and in many cases even basic security measures. Good example make a e-commerce app using x and x technologies, and then disclaimer that this app is just to show how fantastic framework x is. Many frameworks js, php name it have disastrous examples, which are oversimplified for the sake of understandability, and then all hell breaks loose when someone finds out that, for example, by default csrf policy, or authorisation is not implemented correctly or not implemented at all.
- pluma 12y ago
  Yes. This was actually an even bigger problem when I started with AngularJS because the real documentation was woefully incomplete, so there was no obvious way to learn about best practices at all (except that everyone apparently agreed that the examples weren't following them).
Illniyar 12y ago
I haven't seen two-way binding go out the window with scaling. It's still the number one selling point and greatly reduces development time in both small and large applications. The only thing I've seen is that in bigger projects, if there are locations where huge amounts of binding might take place (such as drawing, tables, etc...) you don't use two-way-binding in that particular place. And in any case many of the popular frameworks (Ember, backbone etc... ) also use two-way binding, they just don't support two-way binding on simple js objects. And for that many of the bigger frameworks (
- Offler 12y ago
  > The only thing I've seen is that in bigger projects, if there are locations where huge amounts of binding might take place (such as drawing, tables, etc...) you don't use two-way-binding in that particular place. Sounds like two-way data binding went out the window then...

by pluma 12y ago

mk3 12y ago

Regarding seductive examples. I recently found out, that most of the examples even example apps are lacking best practices, and in many cases even basic security measures. Good example make a e-commerce app using x and x technologies, and then disclaimer that this app is just to show how fantastic framework x is. Many frameworks js, php name it have disastrous examples, which are oversimplified for the sake of understandability, and then all hell breaks loose when someone finds out that, for example, by default csrf policy, or authorisation is not implemented correctly or not implemented at all.

pluma 12y ago
Yes. This was actually an even bigger problem when I started with AngularJS because the real documentation was woefully incomplete, so there was no obvious way to learn about best practices at all (except that everyone apparently agreed that the examples weren't following them).

Illniyar 12y ago

I haven't seen two-way binding go out the window with scaling. It's still the number one selling point and greatly reduces development time in both small and large applications. The only thing I've seen is that in bigger projects, if there are locations where huge amounts of binding might take place (such as drawing, tables, etc...) you don't use two-way-binding in that particular place. And in any case many of the popular frameworks (Ember, backbone etc... ) also use two-way binding, they just don't support two-way binding on simple js objects. And for that many of the bigger frameworks (

Offler 12y ago
> The only thing I've seen is that in bigger projects, if there are locations where huge amounts of binding might take place (such as drawing, tables, etc...) you don't use two-way-binding in that particular place. Sounds like two-way data binding went out the window then...