Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Exploring incremental rendering as the default #481
This issue is to explore what it would take to make incremental rendering the default. I'll be testing in some projects and writing notes here on things like bugs, UX, etc.
Incremental rendering is really 2 things. One is a mutation stream renderer and the other is a reattacher. I would rate the stability of these things as:
In order to proceed with incremental rendering there are 2 main blocking issues. They are:
Use Node.js' http2 module
It's a little bit different from the http module, but there is a compatibility api so it might not be too bad to use it.
Figure out how to handle SSL certs for development mode
Setting up an SSL certificate for local development is a pain. Even for experienced developers. For inexperienced users it's probably the difference between using and not using a framework.
So we need a way to provide one by default, or to create one at build-time or something.
Additionally when you create a self-signed certificate you get an ugly error message in browsers that you have to know how to ignore. This flow needs to be improved.
I'm going to begin working on this soon. This is broken up into 3 main things:
I'm going to start with dom-patch since it's pretty straight forward, it will be broken into separate libraries that do one part:
dom-patch will be deprecated once this is complete, and no longer used in done-ssr.