douglasmoore

Not sure what version I was on. But I did a project in it a few months ago. Everything went smoothly. No issues at all.

I might be wrong but I think you need the onavo VPN installed

Then your YouTube, Snapchat analytics would get man in the middled

No kidding. I wish I knew that a week ago.

Truue

Just want to comment on the first two points as a vercel fan

(1) pooling becomes the solution very early. You get massive speed benefits by keeping a connection open. Hitting connection limits is too easy without it. I feel like a push towards pooling is fine because it has great benefits for scale, speed and reliability. Services like Supabase have connection pooled postgres by default even in their free tier.

(2) nextjs server side data fetching is an amazing feature that deserves it's place in future of web development (the react team agrees since they've added server components). Grabbing data before reaching the client is amazing. If you have a centralized db all the more reason to grab as much as you can in one trip.

Other than that I can agree. I think the advice should generally be to not ever recommend a framework too early or without including its use case.

Current recommendations for the different tiers:

Static: GitHub/cloudflare pages

Server: render.com

Scaled: vercel

Played it today. It's very well done. Scratches my Bioshock itch very well.

The Single Executable Apps should be great for Docker image sizes. I love with Go how I can get images to below 5Mb and would love to see the same happen with Node.

This combined with things like distro-less images should be pretty huge for security as well.