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

171–180 of 189 posts

Re: Angular 5.0.0

#171

Post by sametmax »

eric_b wrote: post #32
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 com…

With vue you don't need vuex for most things actually. Medium sized projects can just have a global vue component they use as a central store and just set and get data on it. Simple. Transparent. Works like a charm for a lot of cases. Actually most people i know are not big enough for anything else.

Re: Angular 5.0.0

#172

Post by NewsAware »

agnivade wrote: post #168
eric_b wrote: post #32

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…

TSX ? Is that some new thing now ? Or you meant JSX ?

T stands for Typescript. Otherwise identical to JSX

Re: Angular 5.0.0

#173

Post by jmkni »

DavidWoof wrote: post #117
rockostrich wrote: post #12

Earlier quoted context omitted.

Has testing components become any easier? I remember having to write a lot of boilerplate code every time that I wanted to test a component.

Not really. Testing components is still really a pain: there's lots of boilerplate and the tests are extremely slow. In a medium-size project, they're far too slow to treat as unit tests: I break out all the TestBed stuff into a separate karma integration test config. Angular is in desperate need of something like Enzyme.

Well if you use the Angular CLI it will generate the boilerplate test code for you, I don’t find them slow to run personally (my dev machine is pretty well specced though)

Re: Angular 5.0.0

#174

Post by jmkni »

hateful wrote: post #8
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?

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,…

There was no Angular 3.

Re: Angular 5.0.0

#175

Post by jmkni »

Yuioup wrote: post #116

I really don't get the hate for Angular 2+. Been using it for almost a year now and I love it. Fantastic stuff.

Likewise.

I think a lot of the hate is down to the naming (AngularJS vs Angular), but at some point you need to just accept that it is what it is and get over it!

Re: Angular 5.0.0

#176

Post by jmkni »

maxpert wrote: post #47

Have recently moved system from TS + Angular 1 to Angular 1.5 and then to Angular 2 (took us solid 1 year and you can still see some traces of older code), by time we finished move to 2, Angular 4 was released! And now this! This is WTF moment of my life.

Moving from Angular 2 to 5 is like moving from AngularJS 1.2 to 1.5.

Re: Angular 5.0.0

#177

Post by gungoman »

Coming from the jQuery and Datatables and Knockout era, I just can't accept the weight and performance of Angular beyond the 1.0 release. I fell in love with Vue.JS (it works like jquery and knockout very similarly)

Re: Angular 5.0.0

#178

Post by sametmax »

tptacek wrote: post #36
Glyptodon wrote: post #27

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

But the build stack you use to compile your code did change. And the store ecosystem.

Re: Angular 5.0.0

#180

Post by azr79 »

eric_b wrote: post #32
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 com…

I disagree, our experience with Angular 4 is very good, we are iterating at very high velocity, at a very large scale (Enterprise Tools, Telemetry, Dashboards, Admin tools), and we wouldn't do it any other way. Testing tools are awesome, so the end product is solid if you use them, and with Lazy Loaded Modules + AOT Compilation the applications are very performant.
Post reply on HN