Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

I Was Wrong About AngularJS

DZone's Guide to

I Was Wrong About AngularJS

Initially, a backbone.js loving developer wasn't impressed with AngularJS. But when you add up the time it saved, it ended up being worth it.

· Web Dev Zone ·
Free Resource

Learn how error monitoring with Sentry closes the gap between the product team and your customers. With Sentry, you can focus on what you do best: building and scaling software that makes your users’ lives better.

Here be dragons

Here be dragons

I started using Angular a few months ago. I hated it. Backbone was so much better.

I cursed Angular every day. Logic mixed with HTML, bits of javascript polluting everything, the organisation of services and modules and controllers and apps and all the things feeling like some old school Java app. And god forbid you try to stray from the path, Angular will bash you over the head.

And I never liked how much logic Angular hides from you. When I work on something, I want to understand the whole system. Having a bunch of “Here be dragons, don’t go here” signposts everywhere feels weird.

How can you reason about your code if half of it is hidden?

There was a case where I spent a whole day chasing down a bug because of that. When you clicked on a thing an unrelated thing cried out in pain and the app crashed.

Turns out Angular was messing up the event cycle and tried to update something before a different thing made it ready to be updated. Yes, very descriptive, I know. But Angular’s “This thing can’t be called, derp” was super helpful too.

Had to wrap a bunch of code in setTimeout. Ew.

BUT!

The past few weeks I poked at Backbone again. My love.

And you know what, I can’t argue with results. Despite everything I hate about Angular on a philosophical level, it gets the job done. Fast.

Getting stuff done with Angular is just so much easier. Especially the simple stuff that I don’t want to think about. Want something to be visible or not? ng-show. Want to display a value to users? ng-model.

And so on.

All these trivial little things that, yes, are simple, and, yes, I can code in my sleep, but with Angular I don’t have to. It takes 10 seconds with Angular, 3 minutes with Backbone.

Who cares right? It’s only 94% quicker. Oh …

It adds up, man. It really does.

And because I don’t have to care about these tiny things, I get to spend more brain cycles on the main logic. It even leaves enough time to deal with the millions of steps of responsibility misdirection between the various controllers.

But man do I hate writing so much JavaScript in HTML. Didn’t we agree to ban onclick= ten years ago?

You should follow me on twitter, here.


What’s the best way to boost the efficiency of your product team and ship with confidence? Check out this ebook to learn how Sentry's real-time error monitoring helps developers stay in their workflow to fix bugs before the user even knows there’s a problem.

Topics:
javascript ,backbone.js ,angularjs

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}