I blame it on Next.js Overall, it is a good framework. I have no problems with Next.js as a codebase.
Vercel is a company that needs to sell a product, however. Since they are selling servers - the profit is to market the value of SSR and how easy it is to deploy to the Vercel platform.
While there are valid reasons for SSR. Static generation and data fetching via API patterns can offer the same performance and more flexibility (like as in building an offline-first "PWA" app)
I would love for Vercel to become better and improve their pricing along with add support for something such as custom serverless functions like AWS Lambda in runtimes other than Node.js -- regardless, Next.js has pretty good compatibility with things such as AWS Lambda or even Netlify.
I know it is very minimalistic and hilarious... But basically we have moved backwards 10/20 years to PHP/Ruby where everything is/was SSR :D
BTW: very interesting and great article, I like the way you have "hydrated" the text with a lot of useful links!
I blame it on Next.js Overall, it is a good framework. I have no problems with Next.js as a codebase.
Vercel is a company that needs to sell a product, however. Since they are selling servers - the profit is to market the value of SSR and how easy it is to deploy to the Vercel platform.
While there are valid reasons for SSR. Static generation and data fetching via API patterns can offer the same performance and more flexibility (like as in building an offline-first "PWA" app)
I would love for Vercel to become better and improve their pricing along with add support for something such as custom serverless functions like AWS Lambda in runtimes other than Node.js -- regardless, Next.js has pretty good compatibility with things such as AWS Lambda or even Netlify.
Yeah -- I think it's not a good idea to make EVERYTHING server-side rendered for sure. I like how Next.js allows us to do a hybrid mix of both 😄
...and thank you! Glad you enjoyed.