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

Angular 2 Final Released

angular.io

Post reply on HN
Print view View original

341–350 of 452 posts

Re: Angular 2 Final Released

#341

Post by filoeleven »

pramttl wrote: post #42
dfsegoat wrote: post #27

Earlier quoted context omitted.

Awesome - thanks so much for this from a team running 1.3 in production (and looking now at moving to 2). Just curious if you are indeed saying that the built-in router allows you to do EVERYTHING you could do with ui-router (nested states / targeted views etc)? I was planning on sticking with ui-router-ng2 when we kick over to angular 2. How about testing? Was that difficult moving test suites over?

I didn't have to migrate tests over since I was started with a fresh project in Angular 2. Angular Router does allow nested states: - https://angular.io/docs/ts/latest/guide/router.html - https://angular.io/docs/ts/latest/api/router/index/Router-cl... I don't quite recall what "targetted views" mean?

I think targeted views means multiple s, which it does appear to support:

> A template may hold exactly one unnamed . The router supports multiple named outlets, a feature we'll cover in future.

Re: Angular 2 Final Released

#342

Post by boubiyeah »

gbog wrote: post #283
Brakenshire wrote: post #190

Earlier quoted context omitted.

I'm just writing a first React app, and read beforehand that it was going to be difficult to choose which libraries to use, and to get them to work together, but I haven't found that to be much of an issue in practice. create-react-app set up all the build tooling, for a router the clear recommendation is react router, and for a flux implementation the clear recommendation is Redux. It feels like there's a well defin…

I replaced react-router with route-recognizer. The later is a simple tool your code is using, has proper documentation and stability, and do not get in the way of automated tests with jest. But react-router changed too much (i.e. removed named routes), has a lot of dependencies (browserhistory, etc), has very poor documentation, and did not allow me to do automated testing at the levels I wanted to. Moreover, it is a…

Agreed, react-router developers try too much to change and add new features to their baby. it has become a bit of a monster. 46KB for a minified router framework...

Re: Angular 2 Final Released

#343

Post by softawre »

h1d wrote: post #169
arc_of_descent wrote: post #145

Earlier quoted context omitted.

Classic sales talk, huh? Devs must be in the thousands, but the users of their apps might figure in the millions :)

Users don't necessarily love the underlying framework being used though.

This just in: billions love javascript!

Re: Angular 2 Final Released

#344

Post by ng12 »

Nemcue wrote: post #175
dfsegoat wrote: post #29

Earlier quoted context omitted.

Remember though, Angular is an (opinionated) framework, react is a lightweight library.

I wish people would just stop pointing this out. While technically true when people refer to React they're referring to the canonical stack that people use (i.e. + Redux).

I don't think that makes a difference. I can take a scalpel to my Redux code without really worrying about how it affects my React code.

This is why I use React + Redux with some Webpack magic -- everything is encapsulated and composable from the ground up.

Re: Angular 2 Final Released

#346

Post by rk06 »

ausjke wrote: post #314
dimgl wrote: post #95

Earlier quoted context omitted.

Why not choose Vue.js? It's extremely simple, fast, easy to get started with, and very similar to Angular.

I like vue.js, the only and biggest concern is that it is a single developer project, I'm deciding between react and ng2 now because of that concern, leaning towards react right now.

Evan has added a dozen collaborators to Vue team. so it is no longer a single developer project.

Yes, the majority of code is still written by Evan, due to speed required. but we know that vue is heading in right direction.

Re: Angular 2 Final Released

#347

Post by skhavari »

bluetwo wrote: post #285
electrotype wrote: post #240

Serious question : Why are SPA frameworks so popular these days? When someone asks "What should I use for web development?", It's now all about React/Angular/Ember/etc. But when I look at how are built the sites I like and visit frequently, I'd say 95% of them are not SPA, they are classic sites where the server generate each page (sometimes with one or two Ajax requests)! The Single Page pattern is great for desktop…

I have to agree with you. HTML5, CSS3, and Javascript have matured to the point where they are very powerful and flexible. I don't always see the point of over-complicating things with frameworks.

Yes, they are very powerful and flexible. These frameworks actually payoff and simplify once your project grows beyond a particular size.

Re: Angular 2 Final Released

#348

Post by premium-concern »

estefan wrote: post #148
0xfaded wrote: post #75

Earlier quoted context omitted.

For anyone wanting to try react in a side project, scalajs has comprehensive react compatibility and it's just awesome. Only downside is trying to hire Scala frontend devs.

Yeah I've been looking at this recently. I like autowire's ability to create typesafe APIs shared across the client and server. Very promising, but not simple to set up... http://www.lihaoyi.com/hands-on-scala-js/#Autowire

You don't need Autowite for that. That's pretty much basic functionality of Scala.js.

Re: Angular 2 Final Released

#349

Post by premium-concern »

cutler wrote: post #161
0xfaded wrote: post #75

Earlier quoted context omitted.

For anyone wanting to try react in a side project, scalajs has comprehensive react compatibility and it's just awesome. Only downside is trying to hire Scala frontend devs.

Extra downside is code bloat. Scala.js on its own just maybe but combined with another major framework - forget it.

The amount of code bloat is offset by optimizing a medium-sized picture.

Re: Angular 2 Final Released

#350

Post by emodendroket »

Nemcue wrote: post #195
NhanH wrote: post #77

Earlier quoted context omitted.

Any chance you can do a quick cons review too? Specifically comparing to the weakness of Angular 1 like bloated complexities, issue with custom directives or scope life-cycle.

Cons: 1. Typescript. If your team isn't familiar with it it's not trivial to get everyone on board. The up-front cost can absolutely be worth it in the long run, but there's some friction in the day-to-day work with managing type definition files and looking up esoteric lint-errors from the Typescript compiler. 2. RXJS. Canonical NG2 should use Observables, and rxjs is not a trivial library to learn the ins and outs…

> 5. Sub-par debugging experience. When you get any errors there's a mile long stack trace filled with rxjs and zone.js garble, making it very hard to actually figure out what's going on. When there actually are custom error-messages they are not very informative,

And they said your angular 1 experience wouldn't carry over.

Post reply on HN