As a VIM user, I hate it.

Server-side rendering is friendly to Search Engine. Even though Google crawler can understand Browser-rendered page now, there are still other search engines that cannot. Server-side rendering COULD have better performance if designed well. I use "COULD" since you may get opposite result if poorly designed.

Dan's twitter https://twitter.com/dan_abramov

Always read through your code before committing.

Yahoo has invented Fluxible to support better SSR, it proves that React has poor performance in server side. It takes a lot of efforts to optimize it, but the gains are not much.

@sandeep As the link states "there are very few places where we're using React to render on the serve". I know that there are quite a few companies put SSR of React into production, but it doesn't change the history. https://twitter.com/cpojer/status/711729444323332096

React.js is not designed for server-side-rendering, even though you can do it. Think twice before you apply it in production. For browser side, I haven't heard any report that the memory pressure is an issue.

Even though I use vim for most of time, I would recommend Code as second choice for coding. One advantage of Code is that you can navigate with keyboard shortcuts in Explorer, compared to Atom and Sublime.

Once upon a time, I am a big advocate of TDD. After I came to Redux/React world, I found that unit testing is basically useless in declarative programming style.