<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>React Europe on Jeroen Nyckees</title><link>https://jenyckee.github.io/tags/react-europe/</link><description>Recent content in React Europe on Jeroen Nyckees</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 18 May 2018 22:00:22 +0200</lastBuildDate><atom:link href="https://jenyckee.github.io/tags/react-europe/index.xml" rel="self" type="application/rss+xml"/><item><title>React Europe 2018</title><link>https://jenyckee.github.io/posts/reacteurope/</link><pubDate>Fri, 18 May 2018 22:00:22 +0200</pubDate><guid>https://jenyckee.github.io/posts/reacteurope/</guid><description>&lt;p>This week I was lucky enough to be part of the React Europe conference in Paris. I would like to write down some of the ideas that resonated with me. To do this I will focus on 3 big themes that seemed to come back in all of the talks.&lt;/p>
&lt;h1 id="context-and-suspense">Context and Suspense&lt;/h1>
&lt;p>Since React 16.3 Context and Suspense are two new features that will shape the architectures of client side React applications. Context is a feauture that has been around in the React API since quite a while. The use of it however has always been discouraged. A simple example that shows the power of it would be to show how we can simplify data fetching with it.&lt;/p></description></item></channel></rss>