or subscribe with
Join 6,200+ readers for one email each week.
Digests » 182
Educative.io hosts interactive courses covering many popular programming topics. We recommend Robin Wieruch’s bestselling “the Road to Learn React” - try a free preview today!
this week's favorite
If you belong to a group that’s underrepresented in tech, now’s your chance.
At DIY Redux with RxJS => RxDx Part 2, I will reveal the internals of some most popular and widely used Redux middlewares. As I mentioned in the first part of the article -which you can find above-, my goal is to do an experiment to combine RxJS and all widely used Redux middlewares into a library which can be found here.
One of the challenges I had when learning Gatsby was trying to understand the Gatsby lifecycle. React introduced me to the concept of a Component Lifecycle, but when I started learning Gatsby I felt at a loss again. I remember looking through example repositories and seeing Gatsby specific files in every project and thinking to myself, “What are these files for? Why are gatsby-node.js, gatsby-browser.js, and gatsby-ssr.js generated in the default starter kit? Can I really delete these files?”
People are often drawn towards using React.js thanks to the benefits of isomorphic (or universal) rendering. That is, the ability to render your single page application on the server-side, send the html to the client and have the client become interactive without having to re-rendering the entire page.
Today the need for apps that gracefully scale from desktop to mobile and everything in between is greater than ever and, at least in my opinion, this is due to the growing interest of developers towards progressive web apps and porting Android apps to Chrome OS.