I haven't used Angular in a while, so I haven't heard about Angular 3 or 4.
What's even weirder is that most people I know using Angular are still using version 1.
Angular 5.0.0
51–60 of 189 posts
Re: Angular 5.0.0
#52Re: Angular 5.0.0
#53Earlier quoted context omitted.
It's not just Angular. To me it feels like everything in the JS world releases way faster than it's reasonable to keep up with these days.
People say this a lot. But the React you write in 2017 is pretty close to the React you'd have written the year the framework was released.
Most of my pain with the React ecosystem happened when people kept rebuilding react-router every 6 months. I managed one upgrade, but after that we gave up and stuck with the old version because it worked well for our purposes.
Re: Angular 5.0.0
#54This 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.
We were in the exact same position and ended up converting to react to escape another potential clusterfuck with angular. This was despite the fact that I enjoyed angular very much but as you said it is certainly scary from business perspective.
Re: Angular 5.0.0
#55This 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.
Vue.js can be a good option for shops coming from Angular 1.x.
I love Vue. I prefer it to React and Angular. But once you get to customizing your use-case (like adding Typescript, State management, or Design frameworks) you start relying on increasingly smaller projects with less and less "maturity". For example I make heavy use of the vue-typed library[1] but it has 47 stars and two contributors.
Re: Angular 5.0.0
#56Earlier quoted context omitted.
To be fair the situation has changed drastically over the past 12 months. After 2.0, AOT got enabled by default, drastically reducing size, then 4.0 drastically reduced size, then the build-optimizer (default with 5.0) drastically reduced size.
There was no clear way on how to do this if you wanted to use universal though. The CLI never supported it for ages. Does it support it now?
It does, there is a wiki page on it.
Re: Angular 5.0.0
#57This 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.
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…
You can go Polymer 2.x or Vue 2.x both feel similar to angular 1.5 `component()` approach. React might be a nice option too but it is probably requires more different way of thinking than the former options.
Re: Angular 5.0.0
#58Lack of compile-time checks for the template (and embedded expressions) is a major limitation of Angular. This may be OK for small projects. For large projects with many developers this is a huge problem. Here's what happens: a developer modifies code he's not familiar with. He introduces a bug due to a typo. He builds the code without errors, and runs the application, and everything seems to be OK. The bug is not fo…
This isn't true and hasn't been true for a while. Angular's ahead-of-time compiler converts the template strings into TypeScript which are then type checked, all at compile time.
Can you put a breakpoint in the template?
In .tsx templates you can.
Templates frequently need loops and conditionals. In the case of .tsx this logic is in TyprScipt so you can debug it just like any other TypeScript. In the case of Angular such logic is written in an undebuggable custom syntax.
Re: Angular 5.0.0
#59This 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.
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…
React+MobX would probably be an easier transition and MobX is easy enough to learn and pretty popular.
Re: Angular 5.0.0
#60All I want for Angular are better error message and better browser-refresh times. Right now on 4 I get a meaningless page of gobbledeguck for most error (b/c of transpilation) and 12 seconds to reload the page.
CLI should be pretty much instant to reload a page.