131–140 of 189 posts
Earlier quoted context omitted.
When Angular 1 was left for dead I went to Knockout. I think it is very similar and also very simple to use.
KO is long dead, but I kinda liked it. After ko and angular 1 I felt right at home with Vue.
Earlier quoted context omitted.
That's surprising to me! My main complaints of Angular 2+ are around testing, but I've had nothing but love for React testing (enzyme, chai, karma) EDIT: whoops, mistyped. We don't use karma anymore in our React testing stack. It's mocha now.
Chai and karma aren't specific to react. I remember using them with angular 1.x back in the day.
Hah, looking now, I realize I mistyped. We use mocha, not karma. Was conflating things
From my colleagues, both front-end developers and full-stack developers, I've heard nothing but criticism of Angular >2.0.0. I would like to hear the other side. If you use fresh Angular, why?
When I used Angular 1, the two way binding was a breathe of fresh air. It was akin to when jQuery first hit the scene and you all of a sudden had selectors. There was a learning curve regarding the "Angular way" (think: $scope, controller, directive), but altogether I was happy with the result and the ideology. I tried Angular 2 and it was a mess. It feels as though the ideology is fighting you every step of the way,…
Add to that the frequent execution and performance issues with watches and we deeply regret having to deal with it now.
Add to that having to learn the painful guts around digest-related executions. Watches fire on init so you have to ignore those first calls. Tests are nasty because timeouts have to be flushed manually, and $q promises won't resolve until you call $apply, etc. It quickly became "WTF is going wrong internally".
Angular 2 is a lot better, but at this stage I think so many former AngularJS/v1 developers went the react/vue route and don't see any reason to return.
Earlier quoted context omitted.
React and react-router are not the same thing at all. They're developed by different teams at different organisations. It's not fair to compare the two.
Of course it's fair. When comparing React with Angular it's only fair to compare the react ecosystem with angular. Nobody ever built an SPA in production with just React.
Earlier quoted context omitted.
That's an improvement, but what about syntax coloring, intellisense suggestions and instant squiggly-lines when you make a typo? These are all important for productivity. You get all this when you use .tsx templates (which by the way, are not limited to React, see https://github.com/wisercoder/uibuilder )
As others have mentioned, this is all possible with Angular >=4, both in WebStorm and VSCode. The main issue is with performance and debugging. Using Angular's AoT compilation is still extremely slow and your squiggly lines take several seconds to show up after you modify a template in your editor. And no stepping through templates either when trying to debug why something isn't rendering properly. But, imho, the big…
https://github.com/angular/angular/issues/17976.
ngmodule makes no sense. why can't the components, providers etc get automatically discovered. ngmodules should not be necessary.
Earlier quoted context omitted.
Angular 2 will not help your team deliver valuable web experiences to customers any more quickly or reliably than Angular 1. Probably almost certainly the opposite. I'd argue most teams, if they're willing to go all-in on an SPA framework (which for most apps is a waste of time and money imo) would be better off with React + TSX. Edit: Vue is probably closer to the "Angular way" with databinding, but component to com…
I disagree. In my experience, developing a REST API and SPA with Angular2+ has been the quickest development cycle I've experienced. Not only is it very pleasant to work in, but the end product for the user is high quality. Vue is great, but it's lack of proper component support makes it a bit annoying to work with. I have just migrated an app that was on Angular 2 RC4 to Angular 5 with little to no migrational woes.…
Wait...what are you talking about?
This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.
I work in a large health care organization and they decided a two years ago to jump on the Angular bandwagon. Well, after some serious growing pains they were able to get it to work. One of the major issues was the "executives" just paid a hefty fee to bring in AEM (Adobe Experience Manager) and anything the teams wanted to do had to be able to integrate with AEM. I won't bore with the details, but it was painful.
After a long journey to get those issues solved, the Angular team came out and said they were going in a totally different direction for Angular 2. One of my responsibilities was to write up a migration path to 1.5, and then how to eventually make a full migration to 2.
Yeah, after I told upper management about the rapid release cycle, they just about choked. No way an org this big can move that fast. At this point, any future projects won't have it and we're in legacy support already for three other projects who did use it.
In short, Angular in all forms is dead here, which is sad.
This rapid pace of major releases is a little scary. We're stuck running Angular 1.x because there's no reasonable upgrade path for us. We're a .NET shop and really like Angular, but after the 2.x cluster fuck, we're now thinking about going with something else entirely.
Could be worth your while to look into Cycle.js It's written in TypeScript and, like Ng2, also heavily based on observables
Projects like ui-grid are dying and ui-bootstrap is dead and they're moving to Angular support only. We're suddenly using tech that's being abandoned a lot sooner than we foresaw.
I have my issues with Angular v2+, though overall it's way better than v1, but I truly hope the same doesn't happen to those making an investment in this new platform.