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

81–90 of 249 posts

Re: Angular 2 versus React

#81

Post by rimantas »

PaybackTony wrote: post #30

This is continuing to shape up to be another one of those preference debates. I prefer the Angular approach, as its end goal is to simply make web markup what it should be: Interactive. The downside being that you're forced into Angular's opinions for better or worse. I don't prefer the more "tangled" approach of React. I call it tangled as it's mixing two flavors in one "view", whether you like it or not: JS and HTM…

  >  to simply make web markup what it should be: Interactive
I guess I missed the memo. When did it happen that web markup suddenly got a need to be interactive?

Re: Angular 2 versus React

#82

Post by JDDunn9 »

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…

I've been using just the custom elements polyfill (6KB gzipped) and love it. I definitely think web components will do to React what querySelector did to jQuery. It's so nice to get rid of the bloat of these libraries, get out of dependency hell, and just write pure javascript again.

Re: Angular 2 versus React

#83

Post by ebidel »

Kwastie wrote: post #19
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…

Why did Google create Polymer? Google isn't using it. This is almost the same 'problem' with "AngularJS by Google", it's almost never used by Google. Edit: The reason I like React more is the fact that Facebook uses it in a high traffic production setting. Edit 2: I think the whole Javascript (or framework) fatigue is just a 'transition problem'. Old tools are getting replaced by new tools, causing confusion..

Non-comprehensive list of Google properties and Chrome-team efforts using: https://github.com/Polymer/polymer/wiki/Who's-using-Polymer%...

Obviously doesn't include stuff in the works :)

Re: Angular 2 versus React

#84

Post by Svenskunganka »

blackkettle wrote: post #76
Svenskunganka wrote: post #59

Earlier quoted context omitted.

I think you're gonna like Aurelia[1]. It's badass compared to Angular 2, React & Polymer. You get this really, really nice feeling of writing pure Javascript. It's smaller than Angular, strictly follows Javascript standards which is soooo nice. No {{bindingVariable}} but instead: ${bindingVariable} // Just like in Javascript template strings! Binding? Sure: Two-way? Of course: One time? Yep: The templating is so simp…

Are there any examples using this in the wild? I couldn't find any 'Sites powered by Aurelia' page on the site. Would be interesting to see some full fledged sites (besides the project site).

Well the docs[1] are built using Aurelia, and it's really cool as it fetches the framework API directly from their GitHub repos via GitHub API and caches it on clients computers.

I am currently in the process of re-building our company website with Aurelia (previously Angular 1.X).

[1] - http://aurelia.io/docs.html

Re: Angular 2 versus React

#85

Post by spicyj »

lomnakkus wrote: post #72
plexicle wrote: post #21

Earlier quoted context omitted.

I should say, my post was more about web components and less about Polymer. Polymer is just one way to do it right now, and you're right, it is opinionated. You don't need a library at all if that's what you prefer. The polyfills are there now and they are solid. Webcomponents.js is small and effective. The simple click-and-select-stuff(...) that you are referencing about are probably specific to some bloated Paper e…

> The polyfills are there now and they are solid. Webcomponents.js is small and effective. This leads to a tangential point which I find somewhat interesting to ponder: If the polyfills are good enough... then why does this actually need to be a browser standard? I'd really like to get to a place where we (collectively) find some sort of minimal API-type "thing" that browsers need to support such that everything else…

This is what the Extensible Web Manifesto is -- an agreement from browser vendors to build in low-level primitives so that things can be implemented in user space:

https://www.w3.org/community/nextweb/2013/06/11/the-extensib...

(Of course, higher-level APIs still get added.)

Re: Angular 2 versus React

#86

Post by spicyj »

JoshMnem wrote: post #79
JStanton617 wrote: post #62

React has a non-open license: https://github.com/facebook/react/blob/master/PATENTS , which basically says that an organization can no longer use React once it sues Facebook for any (unrelated) patent infringement. This is an automatic no-way for React for any major company

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.

Re: Angular 2 versus React

#87

Post by spicyj »

JStanton617 wrote: post #62

React has a non-open license: https://github.com/facebook/react/blob/master/PATENTS , which basically says that an organization can no longer use React once it sues Facebook for any (unrelated) patent infringement. This is an automatic no-way for React for any major company

To be clear: only the patent license ceases, which is something you wouldn't even get in the first place with most other licenses. It may also be that no patents are used in React at all. I personally do not know of any that are. (Disclaimer: Not a lawyer, not speaking on behalf of FB, just my own reading of the language.)

Re: Angular 2 versus React

#88

Post by jfhollingworth »

JStanton617 wrote: post #62

React has a non-open license: https://github.com/facebook/react/blob/master/PATENTS , which basically says that an organization can no longer use React once it sues Facebook for any (unrelated) patent infringement. This is an automatic no-way for React for any major company

That is no longer true. They changed this earlier this year [1]. HN discussion about it [2]

[1] https://code.facebook.com/posts/1639473982937255/updating-ou... [2] https://news.ycombinator.com/item?id=9356508

Re: Angular 2 versus React

#89

Post by eyko »

debaserab2 wrote: post #34
Kwastie wrote: post #19

Earlier quoted context omitted.

Why did Google create Polymer? Google isn't using it. This is almost the same 'problem' with "AngularJS by Google", it's almost never used by Google. Edit: The reason I like React more is the fact that Facebook uses it in a high traffic production setting. Edit 2: I think the whole Javascript (or framework) fatigue is just a 'transition problem'. Old tools are getting replaced by new tools, causing confusion..

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

Re: Angular 2 versus React

#90

Post by qwertyuiop924 »

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…

>Polymer is a fraction of the size

Polymer is a whale. And after Angular, I am NOT getting on another Google-funded hype train

Post reply on HN