r/angularjs • u/RazerWolf • Nov 24 '14
[General] 2 years with Angular
http://www.fse.guru/2-years-with-angular8
u/dmackerman Nov 24 '14
What a garbage article. He complains about 3rd party modules, and then suggests using micro-libraries + 3rd party modules with React and Backbone on his twitter account.
And the performance part? Angular is very performant in most scenarios. Unless your doing something very out of the box, performance should never be a problem - and if it is, your likely doing something wrong.
3
u/roccanet Nov 24 '14
im at about 2 years with NG and i dont agree with a lot of this guys points. ive used drupal, symfony2, django, custom/jquery, and codeigniter in the past with and without development teams and have had better and more rapid success with building an enterprise FE with NG then all the other frameworks on this list. To his point - the learning curve is relatively steep - and it probably isnt the most performant FE on this list - but its fast enough for most anything you might need to do for most web apps. You really get some amazing efficiencies on a team basis if you can run NG with a node backend - everyone becomes a full stack engineer by default.
3
u/jhartikainen Nov 24 '14
I like that he actually took the time to write at least some detail on the bad parts, but I wish the other points would've been discussed in some more detail.
As someone who's been involved in a relatively large-scale AngularJS project for the past year or so, I'm finding I don't really agree with these posts that keep popping up lately, and they are always so light on detail so I can't understand their reasoning either.
2
u/kokomo42 Nov 24 '14
Almost any successful library/framework go through this phase. At one point the hipsters developers start to bitch about it like it is worst then Ebola even though It was the best thing in the world a minute ago
3
u/PandemoniumX101 Nov 24 '14
Most of the remarks here could be utilized across any framework, like most complaints against Angular.
"
1)Teams with varying experience.
2)Projects, which are intended to grow.
3)Lack of highly experienced frontend lead developer, who will look through the code all the time.
"
If you use any framework and don't keep in mind the application will grow, it will be a mess.
The final item of performance I am going to have to completely disagree with. I am in my second year of angular and every performance issue I have ran into has been a fault of my own, not Angular.
So infuriating how many people are shit talking Angular purely on anecdotal evidence. Show me benchmarks before you start complaining about the performance.
3
Nov 24 '14
Angular is the worst framework ever invented except for all the others.
-Winston Churchill
1
Nov 25 '14
Honestly, this is how I feel about most frameworks. We're always searching for the perfect solution but in reality, there is no perfect solution. It's just the one that ends up driving us the least crazy that we pick.
2
u/IMAHiji Nov 24 '14
I read this twice and come up with anything useful. I want the last 19 minutes of my life back...
2
Nov 24 '14
This guys sounds like he knows what he is talking about but I don't completely agree with him yet. Could this be a case of, "Every framework is a cost benefit equation." Short of building your project with no framework, you will have to put up with some level of aggravation. I did not hear many solutions in his criticisms.
I have never been able to do so much with so little code before Angular. In the past I worked with backbone/marionette and felt that the framework helped me with nothing. When you have a tiny team of smart people who need to get things done fast, Angular really shines. That being said I can't imagine how painful it would be to work on a team with junior or intermediate developers with Angular.
1
u/SleepyBrain Nov 24 '14
I can't imagine how painful it would be to work on a team with junior or intermediate developers with Angular.
It depends, but for the most part it's fine. I have friends who work with large development teams, and they seem to do a good job with it. A common approach is to let the experienced engineers take care of the javascript, and make directives as building blocks of sorts, which lets the designer or junior devs just use html to build whatever page they need to make.
2
u/kokomo42 Nov 24 '14
Junior devs are not stupid, the basics of AngularJS are not hard to learn. A simple code review process will be very affective in short time. Like in every project, on any platform, let the strong devs do the complicated stuff and the juniors do the simple stuff. I was not convinced by OP, I still like Angularjs and find it very productive.
2
u/SleepyBrain Nov 24 '14 edited Nov 24 '14
I agree. Honestly I think posts like these are an attempt to generate a controversial discussion of sorts that result in a higher traffic to their blog rather than create a meaningful discussion.
1
u/tsimon Nov 24 '14
This article is disappointing because it's written in a way to suggest that there is substance behind his opinions, but it's not provided. I'm not suggesting that there isn't any substance (I don't know - I happy to like Angular but I'm interested in hearing other people's opinions), but just that it isn't provided.
0
Nov 24 '14
[deleted]
4
u/placidified Nov 24 '14
It's just another week on the Angular bashing train thats going past right now. As /u/Seus2k11 has said "everything has drawbacks".
2
u/CheerMan99 Nov 24 '14
Amen!
-3
u/And7s Nov 24 '14
Who are you and why should I care about your complainment about other peoples compainments.
He's basically giving some ideas/ misconsceptions. If you want to discuss any of these ideas: Think ybout on your own/ your dev team/ the redditors in this thread.
Why should you care? Well, nobody says you should. Either disagree or agree. Just as simple as that.
4
Nov 24 '14
I disagree with posting pointless posts like OP did. If this were /r/politics and someone posted a blog post from some random Republican blogger giving his opinion on Obamacare without providing examples of how to do it better, it would get down voted to oblivion. Why is this any different? Also, as of the Angular 2.0 announcements, every dev subreddit has been on a hate train and it's getting quite old. This blog post was about the bottom of the barrel for me though.
As I said before, if he wants debate then give opinions and examples of how to do things better. If he wants to ride that hate train, then I'd hope as a subreddit we'd be better than upvoting these sorts of posts.
2
u/Seus2k11 Nov 24 '14
Agree 100%. I've used Angular for about 8 projects and have about 2 years experience as well. I have no gripes with using it. Everything....everything has drawbacks.
2
u/TheNiXXeD Nov 24 '14
This is my thought as well. Also, I enjoyed the grumpy cat thumbnail for the OP, lol.
13
u/saggyrampage Nov 24 '14
Could you maybe point out some actual benchmarking? I have been working with it the past 7-8 months and don't see the performance issues you seem to have such an issue with. I think your article does raise some issues with angular but you haven't really backed your claims. It leaves the reader unconvinced.