r/angularjs • u/jeffwhelpley • Nov 03 '14
[General] "Screw You, Angular"
https://medium.com/@jeffwhelpley/screw-you-angular-62b3889fd6787
u/pipituu Nov 03 '14
This is an awesome article. And I agree with it. Unfortunately, having written production apps, I'm done with angular until 2.0. The problem I have with this huge rewrite is also how much the tools I depend on will have to change to conform to new standards.
4
u/djvirgen Nov 05 '14
I don't understand. Is this how you felt about ECMAScript6? HTML5? CSS3? Are you going to abandon a whole project because one tech technology you chose is migrating to a new version?
3
u/joesb Nov 05 '14
You can write most of old HTML in HTML5. You can use only old CSS features in browser that supports css 3. You can use old javascript code in ecmascript6. You can not use old Angular code in Angular 2.
2
u/fyrn Nov 04 '14
having written production apps, I'm done with angular until 2.0.
How? Are you just going to not maintain these production apps? Rewrite them? Do you have an actual plan and reasoning behind it other than "there's a major rewrite a couple of years down the road"?
-1
u/jeffwhelpley Nov 03 '14
Thanks! One thing I would suggest is that you check bad on the progress over the next 6 months. I think you will start to see a wealth of resources crop up including ways to start using some of the 2.0 tooling in your app today.
30
u/cemc Nov 03 '14
I just want 2.0's documentation to be superb...
10
u/ndboost Nov 03 '14
this this this this this this..
12
1
10
u/MachXXV Nov 04 '14
I'm in the middle of a large project with Angular 1.2 (Still need IE8 support for now due to healthcare and international clients), but I'm looking forward to 2.0. I don't understand the fear of change. I've lost count of how many times I've gone through framework and technology shifts that make the 1.x>2.x shift look like just switching bottled water brands. Everything I'm doing at any time is a universe away from what I was doing 2-3 years prior, going all the way back. Use the tools you've got, and use the new ones when they get here. It'll all work out. The quality of your apps ultimately have more to do with your skills than the framework you're using. I remember a time pecking away at a green screen terminal hooked up to a VAX that I would have killed for half of what we've got today.
Now get off my lawn.
1
u/fyrn Nov 04 '14
Exactly this.
I'm not even sure what exactly people are afraid of here. I haven't seen any write-up of specifics on how even the transition would affect them. It seems like "I might have to spend a month on this, two years down the road, so I'd rather spend a month rebuilding/retooling into a different framework now," with no clear advantage or reasoning.
I've been seeing more Ember recently and haven't had a real look at it in at least a year, so I'm also more inclined to consider going a different route if I were to start a new project now but I wouldn't go as far as saying "Angular is dead to me until 2.0 drops."
4
u/TheAceOfHearts Nov 04 '14
After using Angular for around two years, I wouldn't suggest it for everything. Always use the right tool for the job.
I think far too many people (myself included) drank the kool-aid.
After playing around with React and a few other libraries for a few weeks, I've realized that a lot of the "nice" features that angular provides aren't really needed and just end up adding a mental overhead. Specifically, when you have two-way data binding it's very easy to end up with complicated and difficult to test code.
5
Nov 03 '14
I feel better. I think people were freaking out because Google is kind of a psychopath (i.e. Google Reader). Larry Page could be sitting on the toilet some morning and decide "Google doesn't do frameworks, shut down everything!" and no one would be surprised.
2
u/christophermoll Nov 04 '14
The difference being that Reader was a service that required Google's participation. If Google really didn't want to work on angular anymore it'd probably become something of a side project for the main devs, like Bootstrap.
It's open source and there are a lot of knowledgable non-Google devs out there that could easily maintain the 1.3.* branch indefinitely. It's still among the most useful frameworks out there, and looks like it remain so for at least the next year or two.
0
Nov 03 '14
[deleted]
11
u/blowfamoor Nov 03 '14
Replying with substance about the topic is more helpful than being a grammar Nazi.
0
Nov 03 '14
[deleted]
10
u/blowfamoor Nov 03 '14
Add something to the conversation along with the grammar check. I think its just as annoying to point out imperfections and not have something meaningful to say about the actual topic. Perhaps you have written something that we can read? If not I give credit to those who actually try.
0
Nov 03 '14
[deleted]
6
u/blowfamoor Nov 03 '14
Clearly you can dish out criticism but cannot take it. Interesting.
0
Nov 03 '14
[deleted]
1
2
u/Modevs Nov 04 '14
Maybe if the article were on a news outlet/source which theoretically has an editor, fact checker, etc. reviewing the content.
For a blog post, I'm willing to forgive a few typos if the content is substantive.
-12
u/chazzlabs Nov 03 '14
I agree with you. Little mistakes like using the wrong spelling of your/you're or there/their/they're throws off the author's credibility for me.
18
u/[deleted] Nov 03 '14
Best article I've read regarding 2.0, I actually agree with most of it.
However, the Angular team still deserves criticism for dropping off the planet for months between ng-conf and ng-europe. They hyped the hell out of 2.0, released docs, started weekly work logs, and then went silent. In the meantime they changed a huge portion of 2.0 and still don't have any technical details about migration.
I understand wanting to build hype but frankly they started the hype too early and will end up scaring people off of Angular 1.x. Before showing tombstones all over the beloved 1.x, they should have released something to assure 1.x users that Angular is still a good platform to invest in before 2016 (or whenever 2.0 is released).
For example, what are the best practices for 1.3 users today to ease migration? I've heard all the following on Reddit:
Use directives only, no controllers
Use TypeScript - ATscript is superset
Use ES6 and Traceur since 2.0 is ES6
Use Dart instead of Angular JS
Hell, I'm an Angular fan but I've lost a lot of my drive to develop on Angular knowing that 1.x has no future.