Did some of your design decisions (first-class serverless support, Now, network optimizations) penalize you when adding features to Next.js?
Overall we're never limited in possibilities. One of the great things about thinking about serverless support is that it helps ensure pages can scale infinitely, even when on-demand rendering.
For example incremental static generation is partially based on what we could already provide users hosting on ZEIT. Now we're bringing these features into Next.js to allow everyone to take advantage of them.
How do you know what to prioritize in the whole list of RFCs/next features that are going to land one day in Next.js?
Generally we prioritize based on community need. For example the amount of 👍and replies + involvement from the community is very telling as to how much impact we can make by building out a feature we're thinking of.
RFCs also allow for experimentation, as feedback allows us to adjust for community needs.