As has been said on twitter by (among others) Dan Abramov: this is FUD: Microsoft and Google's patent concerns have lead to an updated patent grant Microsoft, Google (also: Apple, Twitter) are actively using React Microsoft and Facebook are collaborating on React Native for UWP. Please take care to research the current status of these issues before spreading more information about it.

Well, it's a bad idea in general, but you can make it less bad. Couple of tips: Take 10 minute breaks every hour Every couple (3-4) of hours exercise for about 15 mins (high intensity interval training really wakes you up for example) Eat low-carb meals (carbs make you drowsy) Easy on the caffeine. When it wears off you'll get really tired. If you can't avoid sleep, have a coffee, and then take a 20 - 30 minute powernap. The nap will free receptors for the caffeine to attach to, so it'll work better after you wake up.

@somu huh, interesting. taking a look at the fix.

Although I want to agree with this, I can't. The problem is that for alot of organisations the levels only correspond to technical skillset, not things like responsibility and mentorship, which is where I think a lot of dissatisfaction comes from. I've in the past hired an engineer who was by all technical measures a better developer than I was, but he was impatient and often deployed code that caused regressions. He was also reluctant to share reasoning behind decisions, leaving him the only one that fully understands some of his solutions.

Small caveat: I'm experiencing issues with code splitting in React Router when combined with server rendering in React 15. The client render will contain null (comment) render, and "discard" server markup. I'm still figuring out where to report this, I'll make a minimal repro soon and start discussion on React Router Github.