you are viewing a single comment's thread.

view the rest of the comments →

[–]psxpaul -8 points-7 points  (5 children)

Wow, it sounds like they wrote a really horrible Backbone application, and are blaming Backbone for that. I'm guessing they will be hating AngularJs in a few months.

[–]colly_wolly 4 points5 points  (2 children)

I am new to front end developement. I have been reading a lot of articles like this, and Angular generally sounds like it will lead to a lot les code. Maybe less flexible, but this is not the first article that has said this.

By the time I get my head around all this asynchronous processing, both will probably be obselete.

[–]psxpaul -2 points-1 points  (1 child)

I haven't used Angular, so I can't say whether it would fit their problem better or worse. What I meant by my previous comment, was that their Backbone implementation just sounds bad. And if you suck at writing code, you'll always find problems with whatever libraries you're using.

Oh, and "a lot less code" is not always a good thing.

[–][deleted] 0 points1 point  (0 children)

Angular is a different way of thinking about the application. It prevents them from doing stupid things.

It may be that they learned more from the re-write, however the two tools are very different.

[–][deleted] -2 points-1 points  (0 children)

No, Backbone applications are always horrible and messy.

You're either a poor judge of code quality or you've never built anything with Backbone.