I think you are conflating multiple things. There's several JS styling libraries have literally zero configuration (and don't involve build tooling, etc). They "just work" out of the box.
Plain pseudo classes are supported (e.g. :hover), but since descendant/child combinators aren't supported, a parent :hover can't change a child style. But any element can still have :hover styles.
For generated HTML docs or websites, this is still not ideal because you have to commit generated code into your master branch.
You can even use Travis to automatically generate and deploy your docs/website, which I find much cleaner and convenient than manually publishing or committing generated code.
It's not a $7 billion "exit". It's an investment for a 20% stake in Didi for $7 billion, which presumably will increase in value as Didi continues to expand in China, especially with less need for ridiculous spending on driver incentives since they will no longer be competing with Uber.
Uber probably had something in the ballpark of 20% market share in China so it sounds like the two decided to simply make peace and become profitable together instead of duking it out for years on end and throwing away billions.
Private contributions don't benefit the greater community unless the project is eventually open sourced.
The contribution graph was a nice way to show off how much one contributes to open source, thereby encouraging folks to contribute to open source projects. It's a vanity metric in the first place, so why not use it to help motivate more contributions to open source software?
Folks have been using React in production since way before version 0.12, which is when Facebook should have released version 1.0. Releasing 1.0 doesn't in any way limit your ability to make changes in the future. It does, however, allow for more nuanced semantic versioning with the full range of major, minor, and patch versions. This extremely is useful for both library authors and consumers.
Better late than never, I suppose, but I just don't understand the pointless sentiment that results in waiting to release a fabled "1.0" release.
I prefer browserify because of its emphasis on node compatibility, first and foremost. I think this narrower scope is a strength because as a result, browserify is super simple to use, works without config, and has a surprisingly small, readable implementation. Seriously, read the browserify source.
Honestly, I think it's pretty lame trying to profit from arbitrage on SW prices like that. $3 per alert? Really?
Great job making an OSS implementation.