yep. the trade-off we're making is that you may occasionally have to fix a waterfall yourself, but in return you get a _truly_ unified component model and much cheaper revalidation (for me number 6 on that list would be 'we don't want to fetch a whole bunch of JSON for unchanged things'!)
Comments