title: Said cons to using Next.js don't seem like they would be any different from other SSR frameworks
body: <p>I've yet to take a deep dive into SSR until now, but I'm about jump in, and first doing some preliminary research to try to get me and the agency going in the most-likely best direction. This is one of the determining factors in choosing Angular, React, or Vue as the company's choice in F/E frameworks which will become our go-to. As it has come to seem like React and Next are likely the best way forward for us at this time. I'm focusing on a few said cons of using Next, as they are things that I want to make sure are not deal breakers.</p>
  <p>In <a href="https://nodesource.com/blog/next-nuxt-nest/" rel="nofollow noreferrer">one particular article</a> comparing Next, Nuxt, and Nest, I am seeing a bullet point where it says that &quot;Next.js is not backend&quot;. Elsewhere it's mentioned that Next should be supplemented with a Node.js server for a backend. My question to this is, is that suggesting that Nuxt and Nest <em>are</em> backend? So there wouldn't ever be any reason to supplement Nuxt and Nest with Node or another server? That doesn't seem to me like it would <em>usually</em> or <em>always</em> be the case. Like somehow Nuxt and Nest are so amazing that they handle most or all of the server needs you would ever have? It doesn't seem like that's necessarily their purpose... Or is it?</p>
  <p>In the same article there are similarly three other bullet points as cons for Next that I have a hard time seeing how the other two frameworks would be any different. The other points are:</p>
  <blockquote>
  <p>• If you’re creating a simple app, it can be overkill</p>
  </blockquote>
  <blockquote>
  <p>• All data needs to be loadable from both the client and server</p>
  </blockquote>
  <blockquote>
  <p>• Migrating a server-side app to Next.js is not a quick process, and depending on your project it may be too much work</p>
  </blockquote>
  <ol>
  <li>More so than the other SSRs?</li>
  <li>It seems like every SSR and frontend would need to load from the client and server. Isn't that the point?</li>
  <li>It seems like migrating any backend to F/E and SSR would not be a quick process.</li>
  </ol>
  <p>I could be wrong, but it seems like these considerations were breezed over in the writing of the page. There would be good reason for noting these cons against the other frameworks just to not give the impression that Next is necessarily a miracle against the other two where development and migration were always going to be a breeze.</p>
  <p>Obviously as a SO question, we would like to avoid opinion weighing in here, which this question seems like it might attract. I am looking for <em>specific</em> information about ways to make me believe Nuxt and Nest are advantageous over Next in these few regards.</p>
  <p>I realize that people who could speak to every one of these SSR frameworks are probably scarce, but if you can speak to one or the other, that would still be very helpful.</p>
  <p>Additionally, the article was written in April of 2019, and things may well have changed.</p>