Yes, no one's forcing you to use that middleware of course! But saying that you don't need to use it because you can write decent code is seriously not a releva

Yes, no one's forcing you to use that middleware of course! But saying that you don't need to use it because you can write decent code is seriously not a relevant reason. The idea behind this middleware is to provide a solution that works regardless of what front-end framework you use. Sure you can do it with decent code and handle fetching data and passing it to your templates yourself, but your decent code will probably work for one single framework, and maybe for just that single application you're working on, and it can get messy! Can you imagine now how much work and time this middleware can save you? Regarding your question about scaling, if your application can handle 200 requests per second, I think it will work just fine even when using this middleware. Expect seeing some benchmarks soon! Also, next versions will provide an option that lets you choose to render your pages only when the request is coming from a search engine bot or a social network scrapper.