Intresting, but WHY are these approaches better. Is that adequately explained?
Angular 2 Core
31–40 of 279 posts
Re: Angular 2 Core
#32Angular 1 developers should see this as an opportunity to abandon Angular and move on to React. React is by far and away the best the market has to offer right now. From my perspective client-side applications are a solved problem thanks to React.
I remember when I looked into React that I was basically writing HTML templates into javascript code. Are there ways around doing that now with React? Because I find that to be a pretty big affront to separation of concerns
Re: Angular 2 Core
#33Angular 1 developers should see this as an opportunity to abandon Angular and move on to React. React is by far and away the best the market has to offer right now. From my perspective client-side applications are a solved problem thanks to React.
Not sure what in react would replace all the other angularjs part not related to directives. How does react deal with routing, web service querying, unit testing, etc... It seems to me that the integrated approach of angular isn't answered by react.
There are tons of javascript libraries that are out there that offer the things you want. In most cases, they are more featureful and more stable than Angular's implementations.
Router - Backbone's router, page.js etc
Web service querying - simple jquery ajax calls or you could use breeze.js, pouchdb etc
Unit testing - React has one built in, but you could use others too.
Re: Angular 2 Core
#34I'm not sure I've seen a framework with such a drastic API change, particularly such a young API. I find that very threatening. Having spent a considerable amount of time learning and working with Angular.js, not only does this appear to be massively breaking changes, but it would also break 3rd party directives which has been a great benefit to building the Angular community. This makes me think that Angular didn't…
Angular was started 5 years ago.. Node was barely a proof of concept, and the JavaScript tooling at the time was centered around jQuery.. version 2 looks to be 1-2 years away, and the changes they make are really nice. I've chosen React + Flux for my current development, but in 2-3 years may well be looking to Angular 2. There's a lot to by critical about Angular... least of which is that it's own dependency system d…
> Angular was started 5 years ago..
quoted just to remind people that Angular as we know it is older than most other single-page app frameworks - even if it only became popular a year or two ago.
Re: Angular 2 Core
#35Angular 1 developers should see this as an opportunity to abandon Angular and move on to React. React is by far and away the best the market has to offer right now. From my perspective client-side applications are a solved problem thanks to React.
I remember when I looked into React that I was basically writing HTML templates into javascript code. Are there ways around doing that now with React? Because I find that to be a pretty big affront to separation of concerns
Separation of concerns is different from separation of technologies. For more details, view Pete Hunt's excellent talk at http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-be...
Re: Angular 2 Core
#36To everybody trying to make this into a tech fight about Angular vs. React/whatever, I've been repeating this like a mantra and even mentioned it in a talk on javascript once[0]:
You can argue about the minor details of the tech stack till you turn green and blue, but Angular wins because it succeeds in the only metric that really counts.
jQuery: (for reference)
5,656 commits
7 branches
122 releases
199 contributors
3,003 commits
10 branches
18 releases
226 contributors
7,490 commits
35 branches
90 releases
412 contributors
5,988 commits
12 branches
111 releases
1,044 contributors I am absolutely confident that they are making good calls and the way they have handled the transition periods so far (and the way they are going about these new "big" changes) only increases my confidence.
I would be very surprised if in a few years, Angular wasn't on the same level of "you can basically assume that it's loaded" as jQuery is.
[0] https://www.flickr.com/photos/valanx/14136669418/in/set-7215...
Re: Angular 2 Core
#37I want to be excited, but at the moment there's just so much new and unknown stuff I'm seeing that I'm just not sure. I don't like the new template syntax; html attributes with parentheses and whatnot just look non-standard and I don't really see why they did all that. I really need to dig into the design documentation and find out the whys behind all of these new features.
ES6 is also new, of course; when I first saw Angular 2.0 code, I didn't like it - mostly due to DI, which instead of a single argument in a simple function, now consisted of three different statements to have one service injected, which just feels non-DRY.
Re: Angular 2 Core
#38Guys, relax and stop whining. You are probably wrong about what is going to happen with Angular, because you underestimate how massive Angular has become. I recently began searching for a new JavaScript job. I don't like Angular at all and I am skipping all positions that mention it. I have to skip ~90% of all ads. Think of it – 90% of companies that are expanding their web development use Angular. So, even if this c…
Is this right? I can't believe for a millisecond that 90% of all new JS jobs relate to Angular, it's a horrible and overblown framework with a high barrier to entry. Were you looking at a particular subset of jobs, a particular industry or in a particular location?
Re: Angular 2 Core
#39To everybody trying to make this into a tech fight about Angular vs. React/whatever, I've been repeating this like a mantra and even mentioned it in a talk on javascript once[0]: You can argue about the minor details of the tech stack till you turn green and blue, but Angular wins because it succeeds in the only metric that really counts. jQuery: (for reference) 5,656 commits 7 branches 122 releases 199 contributors…
React is just newer. Give it some time.
Re: Angular 2 Core
#40Ouch, just spent this month learning Angular... And now 'RIP angular.module, controllers, $scope' etc. Does anyone have some idea about when this launches and when it can be sort of considered stable for building apps beyond mere prototyping? Curious about the timeframe :) Thanks
> Ouch, just spent this month learning Angular
I've found that no knowledge I've gained from learning technology/framework/language etc has ever gone to waste.
Somewhere down the line, the insights gained previously come in really handy or even make something that I thought wasn't possible, realizable.