Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

2 years with Angular

fse.guru

Post reply on HN
Print view View original

11–20 of 216 posts

Re: 2 years with Angular

#11

Post by andybak »

jMyles wrote: post #6

If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?

My front-end guy is totally sold on react/flux.

He came to that decision just after we committed to angular... :(

Re: 2 years with Angular

#12

Post by shawabawa3 »

jMyles wrote: post #6

If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?

HTML and JavaScript?

Re: 2 years with Angular

#13

Post by fruchtose »

xpto123 wrote: post #2

I confess I am an Angular fan. But this article is not Angular specific at all, it stays on a very high-level. Replace the word Angular with any other web framework and the article would still make perfect sense. Not that the article does not have some value, just that it has very little to do with its title.

I disagree greatly. I've used Angular in a team project that spanned several months and went into production at a startup. After reading this article, I realize how much of my experience is reflected in it. I personally experienced each of the problems on his "bad parts" list, except for the name clashes issue (#3). For the last few months I've been telling people that Angular is powerful, but it has an extremely steep learning curve. I've been reluctant to tell people to try it because, why you can do a lot with it, you must baptize yourself in the framework before you can write anything half-decent. It's a little depressing to see someone with deeper experience come out and say it does not get better. But I know that as much as I want to like it, Angular imposes too much for me to actually recommend it.

So, this article is definitely not generic. Maybe, if you're reading at the bottom of the article, you can call it generic, because the advice for future projects is good. But otherwise, it's spot on. I can only hope that the Angular dev team sees this blog post and incorporates the recommendations into version 2.

Re: 2 years with Angular

#14

Post by hassanzaheer_ »

While most of the arguments presented in this article are somewhat valid but I hope with the release of Angular 2.0 majority of the issues will be addressed (though does it make sense to make such drastic changes in the upcoming is another debate and already taken care of at: https://news.ycombinator.com/item?id=8507632)

I'm currently working on a comparatively large webapp built in Angular and it was after about 7 months into the project that we started realising it's pitfalls, and it was very difficult to abandon it then.

So we worked it around by: 1) using one-way binding (or bindonce to be exact) to reduce watches 2) avoiding un-necessary $apply() and using $digest() carefully if required 3) using ng-boilerplate for scaffolding 4) defining our own style guides/coding conventions/design patterns to overcome Angular's bad parts 5) frequent code-reviews that made sure new team members are upto speed with the above techniques

luckily we haven't ran into much issues after that :)

Re: 2 years with Angular

#16

Post by sebslomski »

jMyles wrote: post #6

If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?

Personally, I use Angular for Backoffice tools and Backbone.Marionette for customer facing frontends.

Re: 2 years with Angular

#17

Post by gldalmaso »

"And whar are no-no factors for angular?

    Teams with varying experience.
    Projects, which are intended to grow.
    Lack of highly experienced frontend lead developer, who will look through the code all the time."
I am greatly interested in learning what is the alternative that would be a 'yes-yes' in these bulletpoints.

Re: 2 years with Angular

#18

Post by pedalpete »

andybak wrote: post #11
jMyles wrote: post #6

If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?

My front-end guy is totally sold on react/flux. He came to that decision just after we committed to angular... :(

I was fairly sold on react/flux after trying it because it is very simple and you can build very quickly. I've been trying Mercury.js over the last week as I thought the 'cycle' of flux/react was a bit more than necessary. Your front-end guy might be sold on Mercury next.

Re: 2 years with Angular

#19

Post by gasping »

jMyles wrote: post #6

If Angular is not The Thing (a premise which I have no trouble believing), then what is a Good Thing to perform the task of, for example, consuming Django Rest Framework endpoints and making a frontend of them?

It's ReactJS. See my previous comments and surrounding comments for some discourse.
Post reply on HN