gasping

And what's the deal with giving these projects meaningless names? Gulp and browserify mean nothing to me, whereas gcc and make are basically self-documenting. Can we please stop giving these projects trendy names and instead name them by what problem they are designed to solved?

* https://github.com/gulpjs/gulp/blob/master/docs/recipes/brow...

> If you have callback hell, it is an expression of muddled thought.

No. It's an indication that you're using a FOTM runtime environment. There's a reason why no production-ready runtime uses continous passing / callback models.

It's ReactJS. See my previous comments and surrounding comments for some discourse.

No, just please no. Any moderately competent programmer can be productive in either Java or Javascript (+ Node.js). Javascript may help incompetent programmers feel productive because Javascript has fewer compile-time constraints but in the long run the cost of maintaining code written by an incompetent more than counteracts any perceived benefit that Javascript offers.

This is laughably stupid.

I stopped reading when they substituted a relational database for MongoDB. Nevermind that they both solve completely different problems.

This post must have been written by an incompetent business analyst who feels all warm and fuzzy when he parrots the most popular buzzwords of the month. This kind of shit makes our jobs harder because managers see this stuff and decide that "our next project will be built on MongoDB and Amazon Cloud... it's bad ass rock star tech!"

> powerful, elegant, and future-proof

ReactJS. It's totally unlike Angular and Ember in a good way. You will not regret it.

> you'll never go back to anything else.

React completely changed the way I thought about rich clients. It took me a little longer than 2 days, I went into React with an absolute hatred of anything Javascript and came out 2 weeks later loving it. There is something to be said for a library that can wash away over 10 years of built up anger for a particular technology. It's not just another revamped library thrown into the frying pan, it's a complete rethink of how rich clients can be developed almost effortlessly with code that anyone can read. When I got into react, all I could think was "yes, this makes sense, this is how it should have been all along." Moving into the future I expect most libraries will unify under the concepts introduced by React in the same way that most web applications frameworks are different flavors of MVC.

Angular 1 developers should see this as an opportunity to abandon Angular and move on to React.

React is by far and away the best the market has to offer right now. From my perspective client-side applications are a solved problem thanks to React.

I had to laugh at the revenue estimates based on the peak of a brief social media buzz. Most of that traffic will disappear over the next few days.

What did you do when the infatuation with Angular wore off? Did you see the project through to production release? Was your employer satisfied with the outcome?

Thanks for those resources, I will keep an eye on them.

The new kid on the block is famo.us! Have a look!

That's sort of my problem with these frameworks. A neverending explosion of new frameworks that haven't been thoroughly field tested. Meanwhile existing frameworks move on from their 5 minutes of fame and fall into obscurity / deprecation.