Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 5.0.0

blog.angular.io

Post reply on HN
Print view View original

31–40 of 189 posts

Re: Angular 5.0.0

#31

Post by Bahamut »

ainar-g wrote: post #2

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?

Angular 2+ is much better than 1 - it fixes pretty much all of the warts with 1. On the flip side, there are some tradeoffs, some that is not quite Angular’s fault, although they’re tradeoffs chosen by the Angular team in designing the framework.

Angular doubles down on the component-based model it tried to emphasize in Angular 1. It also is very performant. The main router is much better than Angular 1’s.

I haven’t used Angular in the past 5-6 months though - in my current role, we decided on React, and have been satisfied with it for the most part, although some things have been more painful than if we were to use Angular (testing being the big one), but also some things are simpler too. There’s tradeoffs with whatever library one goes with, but as a whole, Angular is still a very strong choice IMO.

Re: Angular 5.0.0

#32

Post by eric_b »

Yabood wrote: post #14

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.

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 component communication really needs something additional like Vuex. So, really, just use React/Redux and you'll get a bigger community with more real-world apps being built with the tooling.

Re: Angular 5.0.0

#33

Post by interlocutor »

rickcnagy wrote: post #24
interlocutor wrote: post #17

Lack 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 is part of what v5 is fixing by enabling AOT by default in development (and production). AOT compilation converts an Angular template to TypeScript that is then type-checked. So on v4+, an `ng build --aot` performs type-checking. But since that's not great developer ergonomics, v5 has included enough performance improvements on AOT that it's reasonable to enable in development (see "TypeScript Transforms"). And…

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 )

Re: Angular 5.0.0

#34

Post by fareesh »

d2kx wrote: post #28
relearn wrote: post #23

Earlier quoted context omitted.

It's been possible for quite some time. Hard to say why you weren't able to without more information.

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?

Re: Angular 5.0.0

#35

Post by merpnderp »

Yabood wrote: post #14

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.

Vue + Vuex is where we went after Angular 1.x. We're also a C# shop and felt burned by the Angular 2+ changes. We worked with React and really liked it, but it was hard to bring on new devs quickly.

Vue is a lot like Angular with data binding, only about a million times easier to get going than React. Vue + Vuex (feels like a really well thought out Mobx) + Vue-Router and you'll be knocking out slick looking web apps in no time.

Also the vue-cli is like a gift from a more intelligent Javascript writing species.

Re: Angular 5.0.0

#36

Post by tptacek »

Glyptodon wrote: post #27
Yabood wrote: post #14

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.

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.

Re: Angular 5.0.0

#38

Post by btown »

interlocutor wrote: post #33
rickcnagy wrote: post #24

Earlier quoted context omitted.

This is part of what v5 is fixing by enabling AOT by default in development (and production). AOT compilation converts an Angular template to TypeScript that is then type-checked. So on v4+, an `ng build --aot` performs type-checking. But since that's not great developer ergonomics, v5 has included enough performance improvements on AOT that it's reasonable to enable in development (see "TypeScript Transforms"). And…

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 )

Not an Angular user so I don't know how well (or if) this is currently fully working, or is still in development, but: https://github.com/angular/angular/issues/7482 and the demo gif here: https://github.com/microsoft/typescript/issues/6508 display all those features.

Re: Angular 5.0.0

#39

Post by drraid0 »

All 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.

Re: Angular 5.0.0

#40

Post by tashoecraft »

interlocutor wrote: post #33
rickcnagy wrote: post #24

Earlier quoted context omitted.

This is part of what v5 is fixing by enabling AOT by default in development (and production). AOT compilation converts an Angular template to TypeScript that is then type-checked. So on v4+, an `ng build --aot` performs type-checking. But since that's not great developer ergonomics, v5 has included enough performance improvements on AOT that it's reasonable to enable in development (see "TypeScript Transforms"). And…

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 )

...webstorm provides all that, I'd also bet some plugins for vscode and atom do as well.
Post reply on HN