This is huge, because you can’t control your client’s speed, just the amount of data you send to them. Minimizing that, as well as the amount of JavaScript and other assets send over the wire (which remix also helps with) = much faster loading app.
We built a small mirror of our company’s flagship app with @remix_run and presented it in our biweekly engineering team meeting. When I turned the network on regular 3g and the existing app took over 8 seconds to load, but remix returned in less than 2, jaws dropped. 🧵
The paradigm of letting your server (which is likely to be immensely faster down/up speeds than the client’s internet) fetch your data and simply provide to the app what is required for rendering and functionality (a subset of what is fetched) leads to faster speeds for most.
This talk on state machines in remix (including controlling your navigation) by @erikras at #RemixConf was sweet. But what stole the show was the smooth transitions with the code samples in his slides!
Pumpjack Dataworks is looking for 2 new people to join our fully distributed team: a jr front-end engineer (React) and a sr back-end engineer (node/express). Please reach out if you or someone you know is interested!
@drathier @EmmaWedekind @lizardbill I like to review my PR on the PR draft page before hitting the create button to make sure I didn’t leave something stupid in (like a console.log that I used during debugging).