Many of us building single-page apps today use JavaScript module bundling tools that trend towards a monolithic "bundle.js" file including the full app and vendor code for multiple routes. This means if a user lands on any arbitrary route they need to wait for a large bundle of JS to be fetched, parsed and executed before the application is fully rendered and interactive.
This is a little backwards, especially when apps are used under real-world network (3G) and device
| import React, { Component } from 'react' | |
| import { | |
| BrowserRouter as Router, | |
| Route, | |
| Link, | |
| Switch | |
| } from 'react-router-dom' | |
| import { Provider, observer } from 'mobx-react' | |
| import DevTools from 'mobx-react-devtools' |
This is a CFP for ReactiveConf 2017's open call for Lightning talks. If you'd like to see this talk become a reality, please ⭐ star this gist. #ReactiveConf
This proposal is not longer active. Context: https://twitter.com/siddharthkp/status/909818777314902016
This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
This is a CFP for ReactiveConf open call for lightning talks. If you'd like to see this talk become a reality, please ⭐️ star this gist. #ReactiveConf
If you're on your phone, please request the desktop site to star this gist 😇
This is a snapshot for ReactiveConf open call for lightning talks.
If you want to uncover the depth of service workers and how they are revolutionizing the page speed of web apps, please ⭐️ star this gist. #ReactiveConf