> if you don't want or need streaming, then Next.js might not be the right choice for your app. I'm glad to see this stated so clearly. It's important for fram

> if you don't want or need streaming, then Next.js might not be the right choice for your app. I'm glad to see this stated so clearly. It's important for frameworks to be upfront about the use cases being served and the trade-offs that are being made. I think a lot of the negativity that I see on the web is because Next.js was the right choice [for them] in the past, but once it moved towards streaming as the primary paradigm, those same people probably are feeling left in the dust. I think it would be good for the Next.js team to reiterate this and/or make it more clear in the docs so that new devs can make informed decisions when evaluating Next.js for their next project.