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

Angular 2 versus React

medium.com

Post reply on HN
Print view View original

111–120 of 249 posts

Re: Angular 2 versus React

#111

Post by ryanSrich »

onetwotree wrote: post #2

React's learning curve is tiny compared to Angular. With React, you need to understand the component API, which consists of about 5 methods that one uses regularly, and the top level API, which consists of 2 (or just 1 if you use ES6 class syntax to create components). And as the article points out, it's just JavaScript.

I had the complete opposite reaction. I learned a bit of React through a rails + react tutorial and I was lost pretty much the entire time. Having to write HTML using either JSX or the ReactDOM syntax was a complete nightmare. Granted the testing options of both beat out angular, but even at a surface level React just wasn't appealing.

Re: Angular 2 versus React

#112

Post by lomnakkus »

magicalist wrote: post #109
lomnakkus wrote: post #106

Earlier quoted context omitted.

That's a little closer, but AFAICT it's just a bunch of added "signatories" -- again from a skim-read. In the long run, WebAssembly may be it. As of the promised-1.0 it's just a way/excuse to run C/C++ code on the browser's VM with some GL/Canvas mixed in there. I mean, I understand marketing a FPS-game-in-the-browser as the be-all and end-all thing, but that's not my market or end game :). It'll be really interestin…

That is it (and there's quite a bit of thought in those bullet points), but not sure what you're looking for. It's a manifesto for how to approach writing standards for the web, not a standard itself.

That's fair enough, but I guess I just don't think there's enough... commitment in that?

I appreciate the point about meta-standards vs. standards. I think I'm more looking for concrete technical standards (to obviate all others before them![1]) than meta-standards. The web has advanced significantly in the last few years, perhaps even as a result of this meta-standard, but ultimately I'm skeptical that competition between entities that don't have the same goal will "succeed"[2] in any objective sense. The point me be a a bit muddled at this point, but think "principal agent problem".

[1] Because that always works! (Find your own XKCD)

[2] Yeah, I know. Everybody has a different idea of what that means.

Re: Angular 2 versus React

#113

Post by ykka »

mambodog wrote: post #103
plexicle wrote: post #9

To me it really feels like Polymer is taking all of the pros from both of these "libraries" or "frameworks" or whatever you want to call it and none of the cons. Why aren't we talking more about that? Polymer is a fraction of the size. It's one of several ways right now to write custom components. React and Angular2 do the same thing yet they are both bloated and force tons of tools and tech down your throat. For wha…

> This is the year of framework fatigue. This is the year of the framework fatigue meme. Next year is the year everyone realises why we had frameworks and tries to salvage the mess they made last year, when they wrote an app 'without a framework' and ended up with an under-specified, incomplete, undocumented, informal framework.

This is beautiful.

Re: Angular 2 versus React

#114

Post by etjossem »

spicyj wrote: post #86
JoshMnem wrote: post #79

Earlier quoted context omitted.

Yes... I'm really surprised that people aren't talking about this more seriously. They have removed the worst of it, but it still looks like it gives Facebook an advantage in any patent conflicts with any company that uses React, Immutable, Hack, HHVM, GraphQL, etc. anywhere in the dependencies. It appears that the PATENTS file claims that if Facebook infringes on your patents, you can't defend your patents without a…

Google does use React now; as far as I know they are happy with the current version of the PATENTS file.

Citation? Which projects use it?

Re: Angular 2 versus React

#115

Post by dimgl »

Oh my Christ, not this again. The framework fatigue is real. Why are people trying to push Angular 2 or React even? The former is still under heavy development and the latter is such a painful pill to swallow.

Re: Angular 2 versus React

#117

Post by JoshMnem »

spicyj wrote: post #86
JoshMnem wrote: post #79

Earlier quoted context omitted.

Yes... I'm really surprised that people aren't talking about this more seriously. They have removed the worst of it, but it still looks like it gives Facebook an advantage in any patent conflicts with any company that uses React, Immutable, Hack, HHVM, GraphQL, etc. anywhere in the dependencies. It appears that the PATENTS file claims that if Facebook infringes on your patents, you can't defend your patents without a…

Google does use React now; as far as I know they are happy with the current version of the PATENTS file.

The last I heard, they weren't allowed to use it. If you could link to a Google product that uses React, I'd like to take a look.

Re: Angular 2 versus React

#119

Post by doczoidberg »

eyko wrote: post #89
debaserab2 wrote: post #34

Earlier quoted context omitted.

??? https://www.madewithangular.com/#/categories/google

I believe people generally mean that Google isn't using it for any of their core products: Gmail, Search, Google+, Photos, YouTube, Google Play, Calendar, Drive, Maps... none are built with Angular.

adwords is not a google core product? the angular team works together with the adwords team

Re: Angular 2 versus React

#120

Post by jbhatab »

coldtea wrote: post #57

> Sigh. Yes, Angular is a framework, React is a library. Some say this difference makes comparing them illogical. Not at all! Agree. This BS "oh, it's like comparing apples to oranges" knee jerk reaction should stop. For one, even if Angular is a superset, we can always compare the parts that both have: component model, templating, etc. Second, when we say React we almost ALWAYS mean React + Router + some Flux lib, e…

If you're comparing flux + react + router to angular, then I feel like your missing huge aspects of what makes react valuable. I feel like when people talk about the awesomeness of react, they talk about the ecosystem around it.

It's the fact that Facebook has broken up react and all the surrounding architecture in a new way that is modular and logical for sharing code efficiently across various elements of a project or across projects. When I get excited about react, its because of things like Graphql coming out which is an entirely new way of interacting with your server that makes client side development significantly better.

They are creating entirely new ways of how you interact with the server side from the client side. This is why I love react and everything surrounding it. Not because it compares well to some random JS MVC that is completely tied to the DOM like angular, ember, or polymer.

Post reply on HN