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

161–170 of 452 posts

Re: Angular 2 Final Released

#161

Post by cutler »

0xfaded wrote: post #75
gkoberger wrote: post #6

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

Re: Angular 2 Final Released

#162

Post by mstijak »

jasim wrote: post #137
mstijak wrote: post #117

Earlier quoted context omitted.

Have you seen yesterday's post about Cx? I'm curious what you would have to say about it. Cx adds declarative data-binding, controllers and router on top of React and includes composable widgets and charts. It looks for a sweet spot between development speed and freedom to do whatever you want. Here's a quick example https://cx.codaxy.com/fiddle/?f=42vDn4I1 . Disclaimer: I'm the author of Cx.

First impressions: looks like Angular's two-way data binding (using custom attributes in the template itself) added to React. This should make it possible to write complex views quite fast - without writing much code, and yet we don't lose out on the component-based composition of Javascript code offered by React. What I need time to get around to is the concept of controllers and how it works when we want to compose…

Thanks.

Here's an example of a complex lookup field in practice. https://github.com/codaxy/cx-starter-kit/blob/master/app/rou...

It's perfectly fine to add multiple bindings between lookup options and field's data. That works for multivalue fields too.

If you have any other questions I'm happy to answer in this thread https://news.ycombinator.com/item?id=12495728

Re: Angular 2 Final Released

#163

Post by majc2 »

jasonkester wrote: post #120
gkoberger wrote: post #6

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.

I recently started a new front-end-heavy project and ended up just using Angular 1 instead of React. The decider for me was the amount of tooling that React needs you to have in place just to get up and running. React expects you to do your development on some flavor of Unix, and really doesn't have a sane plan for Windows, so you lose VS.NET and its huge productivity gains. And it needs tools upon tools upon tools t…

> React expects you to do your development on some flavor of Unix, and really doesn't have a sane plan for Windows, so you lose VS.NET and its huge productivity gains.

I've done both React projects with Python and C# apis. React is perfectly usable in VS.NET - are you aware of the Task Runner Explorer - https://blogs.msdn.microsoft.com/webdev/2016/01/06/task-runn... - hooks whatever you want into the build cycle, watches etc - once I discovered that, everything just clicked into place.

Re: Angular 2 Final Released

#164

Post by k__ »

boubiyeah wrote: post #158
kayoone wrote: post #21

Earlier quoted context omitted.

I like the opinionated approach of NG2 over the flexibility of React because it takes a lot of decisions off of me that i am not too interested in when building a new project. I am a full stack developer leaning more towards backend in recent years and i found setting up and finding out about best practices and "what to use" for React a bit tedious, also it changes so much. The last Flux framework i used was alt.js w…

You can totally use typescript with React, in fact it's a game changer. It's actually way more beneficial than with angular, as you have properly typed components all the way down. No crappy string templates that are not checked by typescript.

True story.

But how did you get rid of the implicit anys when using JSX?

I used this compiler flag that forbids them and suddnendly nothing worked anymore. It seemed that almost everything returned any per default.

Re: Angular 2 Final Released

#165

Post by k__ »

subsection1h wrote: post #151
danmaz74 wrote: post #136

Earlier quoted context omitted.

Regarding the "Flux" frameworks, that's not a problem anymore - basically Redux (which improves on some of Flux's faults) has won. Its developer was hired by Facebook, so I guess it's kind of officially sanctioned now.

Has everyone who switched from Redux to MobX been informed that Redux won and they should switch back?

I didn't understand this. Isn't MobX the "classical" way of databinding everybody frowned upon for years? And now that React finally eased that pain with Flux and then Redux, they bring it back?

Re: Angular 2 Final Released

#166

Post by pferdone »

jasonkester wrote: post #120
gkoberger wrote: post #6

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.

I recently started a new front-end-heavy project and ended up just using Angular 1 instead of React. The decider for me was the amount of tooling that React needs you to have in place just to get up and running. React expects you to do your development on some flavor of Unix, and really doesn't have a sane plan for Windows, so you lose VS.NET and its huge productivity gains. And it needs tools upon tools upon tools t…

I can not share your experience at all. We are using React with Typescript for our projects at work and we have all common systems present (Linux, Windows, Mac).

Our projects compile from Typescript to ES6 and then ES6 to ES5 through babel. All of that takes place in webpack, and it was pretty easy to setup. We also all use Visual Studio Code and it's a joy to work with.

If you use something like hjs-webpack it gives you (hot-)reloading for code changes out of the box.

Re: Angular 2 Final Released

#167

Post by Grangar »

wcarss wrote: post #8

Is there a definitive angular versus react versus ember (or others) pros/cons/community status page out there somewhere?

Not definitive, but there are a lot of good comparisons:

http://smashingboxes.com/blog/choosing-a-front-end-framework...

https://www.developereconomics.com/feature-comparison-of-4-p...

https://www.developereconomics.com/comparison-4-popular-java...

Re: Angular 2 Final Released

#168

Post by thesimon »

sakopov wrote: post #105
petilon wrote: 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}}…

Why would you want HTML embedded into your component? Sounds like a maintenance nightmare.

So better embed the logic into the HTML? :)

Re: Angular 2 Final Released

#169

Post by h1d »

arc_of_descent wrote: post #145
boxctim wrote: post #123

"Loved by Millions" might be overstating things a bit

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.

Re: Angular 2 Final Released

#170

Post by Kiro »

EugeneOZ wrote: post #39

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…

> 3. Idea of `(events)` and `[attributes]` is awesome, works really effective and makes code much more easy to read.

This is encouraging. I always thought that looked aweful so it's nice to hear that it actually makes sense.

Post reply on HN