What's Next? Exploring the future of React, now - Guillermo Rauch

all right so my presentation today has no slides which is uncommon for me to do but I just couldn't put them together in time hopefully I will do it for reactive calm tomorrow maybe not anyways so my talk is actually about the rest of the spectrum of universal rendering which is dynamic rendering as a matter of fact if anyone has heard of now the

tool that we create for single command easy simple deployment the idea is that you're in any directory you enter now and your package that Jason or docker file gets uploaded to the cloud built and served so that gives you a pretty Universal way of expressing any sort of JSON API website even like a static list of files or whatever and we launched it

initially thinking about JSON API so you can figure a package of jason and you say I put Express in it you press now we give you a link immediately with the feedback about the process then we do the build in the cloud so we run in pain and soul and being starred or duck or build and whatever and we basically reload the page and your API is live so the initial thing we were focusing on was the new micro service opera services

opportunity but very quickly we realized that a lot of people wanted to just do static file hosting so we thought about it and we thought we have two options for doing this it's one is we special case static file hosting so we take a directory and we say oh there's no manifest here so therefore it's static of some sort and the server would handle that appropriately instead what we decided to do is we added a little bit of intelligence to the client and we said well actually a static file hosting

is just adding a package JSON on the fly and using a tool like HTTP server or a serve or list to sort of wrap a little HTTP server around that a static folder or starting list of HTML files and and do static rendering that way and we call that now serve and it turns out that now serve and I'll may I'll get to my main point very quickly it's actually one of our most popular ways of deploying

applications to our cloud so people use now serve a lot and we're very happy with this abstraction because for us as static is really a subset of dynamic anytime you need to do something a little bit more complex like let's say you want to write an API server you want to write a slack board or whatever you have that choice so by supporting the spectrum of dynamic we have static as a side effect another reason we created now was we were kind of frustrated with how long builds took on the client side on the

developer side so there are a myriad of reasons for that one is laptops or iPads or phones becoming developer machines are not gonna be very powerful moving forward a lot of people might start actually coding on their tablets or phones in the future we don't know so we were looking at a future where it's not necessary to have a very powerful machine and we defer the build to the cloud so that was one of the main philosophies and the other one is the internet connection of the cloud is always better than your computers so by

us sending the manifests to the cloud we can make all this awesome optimizations kind of like imagine what yarn does but on a global scale so and what the other reason that we were interested in solving this problem was the machinery that we use nowadays to make Universal rendering possible is very very robust so I was running yarn today and yeah it's faster but I think the total number of dependencies for a project was saying like 20,000 and there were all these