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

151–160 of 189 posts

Re: Angular 5.0.0

#151

Post by chrisco255 »

tptacek wrote: post #142
PKop wrote: post #130

Earlier quoted context omitted.

Checkout Next.js (React based framework) if you want to worry the least about routing, and just default to a route per page model. Next also makes it easy to do server rendering and/or pre-rendering of routes.

You can do this, but routes-per-page with parameters and working back/forward buttons with no serious deps is literally something like 15 lines of code. I think more people should just hack their own router together before introducing a dep for it.

It might be an interesting academic problem to chew on but there's edge cases there with history, route parsing, nested routes etc that are beyond beginner level I would argue. There's something to be said for using a massively popular lib like React Router that the rest of the community is battle testing for you.

Re: Angular 5.0.0

#152

Post by chrisco255 »

vilmosi wrote: post #112
vosper wrote: post #97

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.

Right, I'm sure there's some Rails and Django folks out there just using React as the view layer. Plus as someone mentioned above, Next.js is one of the simplest ways to do full stack React.

Re: Angular 5.0.0

#153

Post by tptacek »

vosper wrote: post #134
vilmosi wrote: post #112

Earlier quoted context omitted.

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.

OTOH I'd be amazed if no-one's built an SPA in production with React and nothing else from the React ecosystem. What would be so hard about that? You can totally use it as just a view layer, if that's what you want to do. Granted, you probably use other non-React libraries, but that's not what we're talking about.

You can also have a "view layer", some control flow behavior in simple higher-order components, and then stores and actions that are simple plain-ol'-Javascript without needing a framework dep. The idea that a React app without Redux and react-router must simply be a brainless view layer is reductive and misleading.

Re: Angular 5.0.0

#154

Post by chrisco255 »

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…

Enzyme and Jest (for React) are pretty awesome. I haven't seen UI testing that good elsewhere...not to mention Storybooks which are great for documentation and manual review. Snapshots, auto mocking, etc...you can't beat React's tooling.

Re: Angular 5.0.0

#155

Post by Bahamut »

FLGMwt wrote: post #92
Bahamut wrote: post #31

Earlier quoted context omitted.

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.

My gripe with testing in React has a lot to do with testing in JS in general - it avoids the elephant in the room of how to mock dependencies (whether it be functions, classes, etc.), and control various scenarios so you appropriately unit test business logic. One can impose a solution by convention with React, whether it be creating/using a DI mechanism, creating functions that one can pass in dependencies to that returns the desired function, or other numerous ways. Or one can choose to avoid creating a solution and decide not to directly test those scenarios, but then that just leads to more expensive, fragile, and complicated scenarios where one loses the advantage of the fast & tight feedback cycle a unit test gives you.

Angular’s solution of a robust DI mechanism is a little on the heavy side, and the test execution perf is worse than Angular 1’s in general, but it is almost certainly the most powerful test helper situation available for testing frontend JS chrrently.

Note that testing serverside JS doesn’t suffer as much, since there are libraries for making use of the require cache for mocking such as testdouble.

Re: Angular 5.0.0

#156

Post by chrisco255 »

tannhaeuser wrote: post #93

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…

I mean, I feel ya. The web was built for rendering PhD research papers, not the complex, rich, responsive apps we have today. Square peg, round hole for sure...but we been hacking away at the hole for sometime to get that peg in there...and today it is feasible to build these things. But you're right that if the web had conceived of being used for rich apps from the beginning we would have been spared a lot of trouble.

Re: Angular 5.0.0

#157

Post by wolco »

apatheticonion wrote: post #100
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 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.…

vue 2 has the best component structure hands down.

Re: Angular 5.0.0

#158

Post by tptacek »

chrisco255 wrote: post #151
tptacek wrote: post #142

Earlier quoted context omitted.

You can do this, but routes-per-page with parameters and working back/forward buttons with no serious deps is literally something like 15 lines of code. I think more people should just hack their own router together before introducing a dep for it.

It might be an interesting academic problem to chew on but there's edge cases there with history, route parsing, nested routes etc that are beyond beginner level I would argue. There's something to be said for using a massively popular lib like React Router that the rest of the community is battle testing for you.

* History: on modern browsers this is ~5 lines of code? Pushing URLs with pushState, triggering PopState events, and binding a popstate handler to trigger render changes.

* Route parsing: just use pathToRegexp. Yes, it's a dep, but it's an easy, well-understood one that does one simple thing you can get your head around. Or: don't use route paths with parameters at all (it's overkill for a lot of applications) and just use a trivial switch statement.

* Nested routes: why bother? The routes we're talking about are totally artificial. Having a formal, declarative route system in the first place is already a lot of "engineering". Just define your routes so they don't do that.

My argument is that the hand-hacked system that does this will be approximately as capable, future-proof, reliable and performant as the first production system anyone builds with react-router will be, the learning curve is shorter, the code you're building won't have APIs shift out from under it, and the final system will be trivial to port to react-router once that library stabilizes, if you ever wanted to bother doing that.

Re: Angular 5.0.0

#159

Post by enraged_camel »

apatheticonion wrote: post #100
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 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.…

>>Vue is great, but it's lack of proper component support makes it a bit annoying to work with.

Sounds like you haven't used Vue recently. As in, over the past year and a half.

Re: Angular 5.0.0

#160

Post by wcarron »

jrs95 wrote: post #91
pygy_ wrote: post #89

Earlier quoted context omitted.

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.

I would say that Vue's core libraries are very well put together. Vuex, Vue-router, vue-resource, vue-axios, etc are all simple and easy to use. Personally, I wouldn't say either community has better supporting libs than the other.
Post reply on HN