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

91–100 of 189 posts

Re: Angular 5.0.0

#91

Post by jrs95 »

pygy_ wrote: post #89
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…

Vue has one big advantage over React for an Angular shop: the views are often trivial to port, while JSX is further syntactically from Angular templates.

IMO the difference in the quantity and quality of packages available for React more than makes up for that difference.

Re: Angular 5.0.0

#92

Post by FLGMwt »

Bahamut wrote: post #31
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…

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.

Re: Angular 5.0.0

#93

Post by tannhaeuser »

Congrats to the new release! I've got a lot of respect for putting so much energy into open source projects.

Predictably, the discussion evolves around Angular vs react/vue/ember or whatever (personally, I like react).

My current customer project introduced me to a new generation of web front-end developers specializing in a particular framework (react/redux in our case) but know very little about CSS and the myriad of plumbing and polyfilling going on in browsers. In the end, they delivered an app that would only run on Chrome. Sadly, the whole thing makes me realize just how utterly inadequate the web platform after all these years still is for the kind of MVw apps folks want to use it for.

I think there's a place for a new "opinionated" web framework once again which more closely matches the needs of business apps, and which has an option to stand-alone app deployment outside web browsers. Mind you, this isn't a sentimental reflection on Java applets and their failure or some such, but based on years of actual project experience, including in front-end developer roles.

For example, the other day I learned that in 2017 there's no way to query the current zoom level of a web app (until very recently with the brand new Viewport API; but it's not supported using media queries; I mean, seriously?). Furthermore, I'm using a very simple SVG background image for a text area element, and the latest Chrome release introduced laughable aliasing bugs, which I could only workaround by using `opacity: 0.99`. There are still just so many tricks and hacks necessary for even the most basic of UI tasks that a realistic web app project feels like jumping from one ridiculous issue to another, frantically searching through StackOverflow, CSS-tricks, etc.

With the somewhat naive reception of react, Angular, and co (which don't actually do anything GUI-related, nor help with browser compatibility problems), I'm wondering whether I'm the only one feeling like putting square pegs into round holes using the web for anything other than content-driven sites.

Re: Angular 5.0.0

#94

Post by cpursley »

philippz wrote: post #84

I somehow do not get all that bashing. Angular did extremely great things with Angular 1 (back then). As time passed, the community learned that there are better/other concepts. React came out - nice. NG2/4 therefore had to include major changes to pave the way for the future and more modern concepts. And it is important that they do that because some people have built huge teams and applications based on Angular. So…

> ng5 fixes major issues from ng2

Good grief, this is insanity. I'm still dealing with major issues in ng1.

Re: Angular 5.0.0

#95

Post by ferdbold »

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.

I don't agree. react-router has changed enough in the last 2 years to throw me off quite a bit when I started a new project

Re: Angular 5.0.0

#96

Post by ferdbold »

Raphmedia wrote: post #77
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.

Angular, React, etc. are nothing but a bunch of pre-written lines of code that does data binding. Quality lines of codes with a lot of candies, but in the end it's only a bunch of JS lines. There are no obligations whatsoever to keep your project cutting edge and even less of reason to migrate to a more popular framework. It's not as if browser support for Angular 1 would stop.

True, but it's nice to be able to use the newer features of your framework as they come out. Positive QoL changes in an API are always welcome

Re: Angular 5.0.0

#97

Post by vosper »

ferdbold wrote: post #95
tptacek wrote: post #36

Earlier quoted context omitted.

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.

I don't agree. react-router has changed enough in the last 2 years to throw me off quite a bit when I started a new project

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.

Re: Angular 5.0.0

#98

Post by dbbk »

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'd consider Ember to also be a top choice (if not the top choice) for teams who want to just go all-in on a framework and reap the productivity benefits. From all the frameworks I've tried, it's the one that's allowed me to focus the most amount of my time on actual product code, not plumbing.

Re: Angular 5.0.0

#99

Post by jurgenwerk »

dbbk wrote: post #98
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…

I'd consider Ember to also be a top choice (if not the top choice) for teams who want to just go all-in on a framework and reap the productivity benefits. From all the frameworks I've tried, it's the one that's allowed me to focus the most amount of my time on actual product code, not plumbing.

So much this. With Ember you can truly focus on shipping features.

Re: Angular 5.0.0

#100

Post by apatheticonion »

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

The transition from Angular1 - Angular2 sucks, but ng2 and beyond is trivial.

Post reply on HN