First, Youtube and Vevo are *NOT* angular applications. Second, pretty much everything that can be applied to Angular in terms of technology can be applied to React. The difference being you choose your legos with React and can easily replace them as needed, where with Angular you will be fighting a multi-tentacled beast in order to change out anything.
I'd also add Walmart and Netflix to the React camp.
As to following Redux as a pattern being hard... there is a little more cognitive overhead, yes. However, once you understand it, you can continue to add a *LOT* of features, while maintaining the exact same patterns and very little additional complexity. By contrast, most other applications look like Spaghetti after they take on new features and grow.
On Ruby on Rails, the examples given are actually examples where it specifically hasn't worked or scaled well and required major refactors and shifts away from Ruby and RoR.
On Databases, There are many other options, and usage will depend on needs and scale. It's specifically worth mentioning that MySQL/MariaDB and Postgres have the most widely available managed options on each of the popular cloud providers. MongoDB is also widely available though will take other considerations vs traditional rdbms.
On Web servers. It's worth bringing up high availability and reverse-proxy options. Many cloud systems would have you deploy your applications on the native platform, and use a reverse-proxy configuration for edge servers.
Been using this for a while, since `label > input... + span` are natural target paths. This way you can effectively "hide" the input and put a prefix content before the span for stylized checkbox value.
NOTE: some browsers would not allow hiding the checkbox, so in that case, setting the position and opacity are your only real options. This isn't much of an issue today, but IE6-8 were particularly nasty in various ways.
Of the posts that aren't spam, over half are from new users created for the post. Limiting to 1 a day until reaching a certain karma would be a good idea. The codebase is sinatra+redis, and I haven't even had the time to get it running to play with.
Unfortunately, I don't see most of the options for automating a way out of spam working much, just because of the smaller scale of the site and the nature of posts (legit and spam).
I've deleted most of the spammy posts I've found... would love to get a change for double karma back on downvotes on articles that are then deleted.
2. Gotcha... there's just so many new takes on this, with what at a glance are very minimal changes to existing options it's hard to gauge.
3. Very cool that you've been able to get that level of involvement. I tend to be skeptical when I see that many upvotes and no comments, and only a very thin readme.
1. out of order on this. It would be a good idea to spell out some of the differences like that. Inferno[1], iirc is a about 8k min+gz, it's also one of the fastest frameworks out there for react-like use. MobX[2] is a pretty decent state machine built around E6X proxies and is a pattern not too dissimilar from your own. I'm more of a Redux fan, but can see the appeal.
I didn't mean to come off as a condescending ass. I just see so many me too frameworks that support JSX and minimal state machines that don't really provide much over what's out there and relatively popular already.
Overall, would just suggest expanding the README.md to include a bit more on the reasoning, and a multi-layer example in addition to the minimal one and maybe a canonical todo-mvc[3] example and an implementation of the benchmarks inferno.js[4] covers.
[1] https://www.infernojs.org/
[2] https://mobx.js.org/
[3] http://todomvc.com/
[4] https://www.infernojs.org/benchmarks