New syntax is ok, quite cool actually, but I'd rather see more improvement on things like route, high performance repeat. Hope they bring some goodness from Angular 2 to Angular 1x as well. Also, not sure how the old directive/plugin ecosystem would fit in, is there any rewrite needed?
Angular 2 Core
111–120 of 279 posts
Re: Angular 2 Core
#112Earlier quoted context omitted.
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.
> There are tons of javascript libraries that are out there And there you have your answer :) What the JS people don't seem to grasp is that I don't care how many libraries are out there. I care even less about the incompatibilities and the different release cycles of all those libraries. By now, I hope you understand that my interest in maintaining and integrating all those into a coherent system approaches zero. I…
> The front-end is just 1-10% of any serious system and yet, in the JS world, it takes 90% of the time building it and maintaining it. It just doesn't add up.
Wow, I want you to come work for me for a week. The front end is what interfaces with the user - your client - the one whom is paying money. You may hate JS, but it is the tool that we use to build interaction.
Re: Angular 2 Core
#113Is he using TypeScript or ECMAScript 6? Also, is it just me, to does this seem like a completely different framework than Angular 1?
Re: Angular 2 Core
#114Is he using TypeScript or ECMAScript 6? Also, is it just me, to does this seem like a completely different framework than Angular 1?
Typescript is ECMAScript6, with additional (typing) features.
I'd venture it's ecmascript 6 being used, as Google suffers NIH syndrome too..
Re: Angular 2 Core
#115Even though this is still called "Angular", this new version has barely any resemblance with the previous one, it's really a totally new framework. It's a bit sad to think that all this knowledge I have of Angular 1 is now obsolete but I'm excited to dive into this new framework. If it's half revolutionary as Angular 1 was, it's going to be a pretty interesting time.
I think it is pretty exciting, in a way it is about the migration off the desktop. Over the last year we have transitioned from WPF thick clients to a SOA with a SPA front end using Durandal. Using Durandal along with knockout felt very natural to us. We chose Durandal in a large part because it was written by someone that thought like us and leveraged years of desktop best practices and applied it to what we viewed as the "wild west" that is web development. Glad to see Durandal concepts will be making it into a great project like Angular [0], Hope it is a peaceful revolution.
[0] http://eisenbergeffect.bluespire.com/angular-and-durandal-co...
Re: Angular 2 Core
#116is there a video of this? viewing these slides is like reading every-other page of a book :(
Re: Angular 2 Core
#117I'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…
I agree. There is virtually no way you can smoothly upgrade an Angular 1 project to this. You'd have to redo most of it from scratch. There are a lot of huge projects that are built on Angular 1 -- many enterprise products too. And this is a huge blow to maintenance. It might be a reason for a lot of people dropping Angular and going for something that makes more business sense. Maybe it's React's time to shine.
Re: Angular 2 Core
#118To 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…
[deleted]
Re: Angular 2 Core
#119Earlier quoted context omitted.
> it's a horrible and overblown framework with a high barrier to entry Listen, if I can figure it out and get lots and lots of work done with it, it's neither horrible nor overblown and the barrier of entry was there but I got over it. By all means, keep ignoring it, but drop the shtick where you know better than thousands and thousands of us out here building things with it.
Hey pal, drop the chip on your shoulder. Just because AngularJS has wide adoption doesn't change the fact that it is an extremely poorly designed framework. I also refuse to consider AngularJS jobs. Many developers have had to suffer through bad frameworks like GWT because of industry trends. Those bruises are not badges of honor. ReactJS is a framework that is clearly better designed. Why waste time learning and suf…
I don't have a chip on my shoulder. It just reminds me of that old comeback for people who are complaining about how terrible PHP is - "oh, I'm sorry. I couldn't hear you over all the work I was getting done with it."
> Why waste time learning and suffering through AngularJS absurdities when ReactJS exists?
Because I'd have to suffer through learning and integrating Backbone or Flux in addition to React to accomplish what I could by learning just Angular. And then I'd have to hope that my choices remained compatible with each other through version updates. Anyway, I may find React to be a better designed lib when I get around to using it, but it's definitely not an apples to apples comparison when it's only attempting to tackle 1 of the pieces that Angular handles.
Re: Angular 2 Core
#120Earlier quoted context omitted.
> it's a horrible and overblown framework with a high barrier to entry Listen, if I can figure it out and get lots and lots of work done with it, it's neither horrible nor overblown and the barrier of entry was there but I got over it. By all means, keep ignoring it, but drop the shtick where you know better than thousands and thousands of us out here building things with it.
>if I can figure it out and get lots and lots of work done with it, it's neither horrible nor overblown That's a weird argument. Just because you think it's not horrible or overblown doesn't really mean much. That's just an opinion. I've worked full-time with AnguarJS over a year, and I know it pretty well. It's easily better than jQuery spaghetti code, and probably better than most data-binding frameworks. It has lo…
> That's a weird argument. Just because you think it's not horrible or overblown doesn't really mean much. That's just an opinion.
A contrary opinion to the OP's opinion. Are you asking me "where's the data" (?), because this whole thread is opinions.
edit:
> It has lots of issues, though.
No argument here. Providing validation feedback on forms, for instance. I'm not arguing that it's perfect and that I'll never love again, but it has opened up my head this year and for that I'll go to the mat for it.