What does HackerNews think of react?

A declarative, efficient, and flexible JavaScript library for building user interfaces.

Language: JavaScript

#1 in Front end
#12 in JavaScript
#1 in Library
#3 in React
It's worth pointing out:

React[0]: JavaScript front-end web framework from Facebook. For good or ill, the most widely-used web framework in the world.

Not to say that Facebook will maintain Sapling, but React does stand as proof that they're not incapable of carrying an open source project to the finish line.

[0] https://github.com/facebook/react

It would at least be far less of an issue. I don't see anyone being confused that https://github.com/facebook/react is the official repo, and not https://github.com/react/react. It's the fact that a collapsed name is a shortcut that imbues it with this special stature. And i believe maven central doesn't even allow one-segment group names for new libraries, though clojars obviously does.
> Doesn't 'fix' already mean there was a bug, that was 'fix'-ed?

Read this: https://stackoverflow.com/questions/3580013/should-i-use-pas...

TLDR from the Git repo: Describe your changes in imperative mood, e.g. "make xyzzy do frotz" instead of "[This patch] makes xyzzy do frotz" or "[I] changed xyzzy to do frotz", as if you are giving orders to the codebase to change its behavior.

People have different opinions on what tense to use, but the one that scales better would be in imperative mood. See example here: https://github.com/facebook/react

The same reason React is under Facebook's github org? https://github.com/facebook/react

FYI, as I commented below, it's also available on Github under its own user and with a very permissive (GPLv2) license: https://github.com/corretto/corretto-8

The Stack Overflow developer survey showed that React and Angular are neck to neck so there's obviously a lot of people who use it.

However, you can see just how popular React is by number of npm packages that depend on it: https://github.com/facebook/react

You are comparing a view library (react) with a full framework (ember). Ofc you are supposed to pull things together with react, that's exactly what's intended.

Compared to react, ember is: slow (1), more difficult to learn (2), has a much smaller community (3) and, most important aspect to me, has a huge footprint (4). (I'm not against ember, it might have some nice aspects and features. It was really nice during the time when they released 1.0. But today I just think their are better options available)

1: https://auth0.com/blog/face-off-virtual-dom-vs-incremental-d... 2: https://guides.emberjs.com/release/ 3: https://github.com/facebook/react vs https://github.com/emberjs/ember.js 4: https://gist.github.com/Restuta/cda69e50a853aa64912d

I know, which is why I said they have a common history and core. react and react-dom are both part of the same github project at https://github.com/facebook/react. Frequently when people are talking about React, they only mean the HTML version, not including React Native. For example, the Nerv project mentioned in this post.

While React Native makes use of the react core package, it is a separate github project http://facebook.github.io/react-native/

Google trends can be quite hard to read - that search term will include Angular 1, which is far larger than Angular 5.

Github stars is a more precise metric. There, react has 80K, Vue is close with 72K (and gaining ground), and both are far ahead of angular on 30K (as of early November 2017).

https://github.com/vuejs/vue https://github.com/facebook/react https://github.com/angular/angular

Keep in mind that part of what makes reading code beneficial is that it's not necessarily easy- in fact, it's often rather hard! The benefit is developing a set of "mental heuristics" to figure out what parts of a codebase are useful, so that when you have to dig through someone else's code you can figure it out just a little bit faster.

That said, here are a couple suggestions. I'm not sure what you use other than C# (and Javascript?) so I'm just gonna link things from several languages.

redis-rb [1] is the 'official' Ruby client for redis. (For that matter, I've always heard that redis itself [2] is a good example of C code.) React's source [3] is rather difficult to figure out, but the team recently released a codebase overview [4] which might help. Alternatively, preact [5] is relatively straightforward, and IMO is a good example of structuring an ES6 codebase.

Rails [6] is ridiculously huge, and has established a bunch of its own conventions for file loading, but on the flip-side it is extremely well documented. To take a single bite of the elephant, take a look at its ActiveJob [7] sub-framework.

1: https://github.com/redis/redis-rb

2: https://github.com/antirez/redis

3: https://github.com/facebook/react

4: https://facebook.github.io/react/contributing/codebase-overv...

5: https://github.com/developit/preact

6: https://github.com/rails/rails

7: https://github.com/rails/rails/tree/master/activejob

Can't say I agree personally on UI Grid - it's a bit of a mess in some ways, especially in its distribution. It is also a bit of a configuration nightmare.

For high quality JS, I would look to some of the major frameworks out there:

https://github.com/facebook/react

https://github.com/angular/angular.js

https://github.com/angular/angular

There is a lot one can learn about software design by reading the source code of major libraries, and is far more reliable than any third party library in the ecosystem.

>Virtual DOM approaches never really were about performance.

"React abstracts away the DOM from you, giving a simpler programming model and better performance" https://github.com/facebook/react

It seems strange to me that many developers are now trying to convince everyone that vdom wasn't selling as a way to get better performance. Yes, getting rid of data changes over time is important property of vdom approaches, but when all this vdom hype were started, everyone is also talked how awesome it is in terms of performance.