Live data from Hacker News

Angular 2 Final Released

angular.io

211–220 of 452 posts

Re: Angular 2 Final Released

#211
post #141

Earlier quoted context omitted.

Of note, Facebook's create-react-app provides an "official' opinionated approach. https://facebook.github.io/react/blog/2016/07/22/create-apps... There's even a pull request to bring typescript into the mix. https://github.com/facebookincubator/create-react-app/pull/5...

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…

[deleted]

Re: Angular 2 Final Released

#212

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

For big enterprise projects where there are many average developers, a full framework like Ember.js or Angular2 is practically easier to maintain.

Especially Ember. Probably Ember is the best choice nowadays for serious project. Great documentation and very matured.

Re: Angular 2 Final Released

#213
post #2

Front end development is crazy these days. I remember on my road to learning Java EE banging my head on the wall trying to put together things like dependency management with Maven, ORM's, and all sorts of arcane concepts and patterns. It took me a long time to get to that point but now it seems all too familiar. As someone coming up to speed with frameworks like React and Angular 2 it feels like that all over again.

If you use Ember.js, which is the most matured and serious on the market, you never had that feeling that JS changes a lot. Consistent and continuous improvement. The best choice.

Re: Angular 2 Final Released

#214
post #48

I evaluated React and Angular 2 several months ago and picked React. Some of the issues I found in Angular 2: The HTML template in Angular 2 is stored in a string. This has several disadvantages: 1. Editors can't do syntax coloring. 2. Editors can't do auto-indenting. 3. Editors can't offer "intellisense" suggestions. 4. Editors can't match tags. You embed variables in this template string like this: ' {{hero.name}}…

You probably missed the best option: Ember.js. It has all the best from other frameworks and it looks the only serious player out there.

Re: Angular 2 Final Released

#215
post #95

As someone who uses Angular 1 currently but would pick React for their next project, I'd love to see a list of reasons why I should use Angular 2 over React. If nothing else, Angular just stranded all their developers, while React has a huge head start on mindshare/plugins/tutorials/etc.

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

I have used knockout, angular, react for a while. When I used vue.js the first time, I smiled. It made me happy.

Re: Angular 2 Final Released

#216
post #195
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…

> I tried to stay very far away from Angular 1 since I found its documentation to be very low quality (probably a symptom of Angular 1 being poorly engineered as well).

I haven't found either of these to be the case. Is your experience recent? If so, will you expand on it? I like Angular 1(.5) quite a bit, but I'd be interested to hear more about a different perspective.

Re: Angular 2 Final Released

#217
post #77

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

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.

Filter and order by pipes removed :) (for a good and documented reason, but still something I've been missing)

Re: Angular 2 Final Released

#218

How does the Angular CLI compare to the Ember CLI? Also, how does Angular 2 compare to Ember 2.8?

Angular CLI is actually Ember CLI under the hood.

You cannot really compare these frameworks because Ember is far ahead of all. Super stable, matured, adopted the best practices, huge addon ecosystem, brilliant community, easy to learn, great documentation. Quite an obvious abd best choice. Life and development is just super easy and fast with Ember.

Re: Angular 2 Final Released

#219
post #189

I use Angular 2 in production since November 19, 2015 (alpha.46). Currently I've built 3 web apps (40, 60 and 20 components each), 3 mobile apps (with Ionic 2) and my employer have plans for more apps. Breaking changes during alpha stage were expected, so I didn't have issues with it. Most positive things I want to highlight: 1. Components are encapsulated and truly reusable (and without dependencies hell). 2. You do…

I haven't used Angular yet. From it's description it seems to be geared for making single page apps. Or a app with a few pages because it's good a binding data to an interface. Is this accurate? What is a good use case for Angular?

I have used Angular in multi-page application, using Angular as a better JQuery in Spring MVC application. This setup worked well combining the best of both frameworks. Angular provided two-way binding, rendering templates (in loop), dialog box interactions, better AJAX, etc. Angular based component libraries provided calendar controls, dynamic tables, etc. Spring took care of the routing pages, handling UI requests and returning JSON response from services.

Re: Angular 2 Final Released

#220
post #135

It is interesting how people are debating here, angular this, react that... Yet there is Polymer that just works, has a great ecosystem, awesome material design support and is a breeze to work with (+ its fast too). Right now there was 2.0 announcement and new version really supports easy migration path unlike Angular 2.x.

Polymer also has a lot of negatives - it still only publishes on bower for example, and the whole vulcanizing situation is sort of bleh. It also uses HTML imports for its components, which is unnatural and sort of munges concerns with the whole ES module import system - this includes importing HTML files for more traditional things such as XHR.

To me, all these things put Polymer far behind the curve as something I'm interested in ever adopting.

Post reply on HN