News for hackers. Stuff that matters.
Re:I won't be using Angular for my next project by sownkunz on Sunday April 05, 2015 @06:57PM (#9325612)
We use Angular on our application and I can't stand it. The only thing I like about it is how well testing is built in to the framework. Beyond that it is far too complicated. Once your project really grows and you've got a huge Angular codebase, with the sometimes inevitable rushed pace you need to work in at a company, it just becomes a disaster. "Scope" crap everywhere that you have no idea where to find what you're looking for.

Definitely would look into something else for my next project.

Re:I won't be using Angular for my next project by cheriot on Sunday April 05, 2015 @07:13PM (#9325657)
> "Scope" crap everywhere that you have no idea where to find what you're looking for.

A framework can't stop people from writing bad code. With Angular (or any other framework) you need to build the object model independent from the controller and template. The dependency injection makes this really easy. Then you've got logic that can be tested in plain unit tests and only a couple objects assigned to the scope (the roots of larger object graphs).

Re:I won't be using Angular for my next project by BinaryIdiot on Sunday April 05, 2015 @07:22PM (#9325676)
This is what I've run into on every Angular project I've been thrusted into. It goes from a somewhat decent separation to absolute chaos incredibly quickly. While that's the developer's fault I don't feel like Angular lends itself to extending and revising existing applications very easily.
Re:I won't be using Angular for my next project by EugeneOZ on Sunday April 05, 2015 @07:51PM (#9325745)
This guide can help to keep code organized: https://github.com/johnpapa/angular-styleguide
Re:I won't be using Angular for my next project by EugeneOZ on Sunday April 05, 2015 @07:50PM (#9325740)
You can write code without $scope since version 1.2. It was few thousands years ago.