NextJS Is Hard To Self Host
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
We did it?
ThePrimeTime
102.6k views
Giving in to the AI Hype
ThePrimeTime
201.9k views
Stack Overflow Is Almost Dead
ThePrimeTime
234.8k views
HARD truths before switching to Go
ThePrimeTime
355.4k views
JUST USE HTML
ThePrimeTime
327.7k views
Linux Is Obsolete
ThePrimeTime
184.8k views
Devin Is A Lie?
ThePrimeTime
240.2k views
C++ Is An Absolute Blast
ThePrimeTime
303.3k views
PHP 8.4 Is Good
ThePrimeTime
168.5k views
Maybe HTMX Is Bad...
ThePrimeTime
161.7k views
Top Comments (10)
The timing of this video is interesting. Lee Robinson (the VP of product at Vercel) just uploaded a great tutorial on how to self-host Next.
I love how this channel doesn't pay lip service to Vercel & the likes but instead focuses on the freedom of technology. I'm not even a professional programmer, but I enjoy this very much.
Love that framing of the capability from owning a deployment platform and being able to use two ways to solve the problems
In other news, Rails is literally optimized to work out of the box for a single developer
15:45 In summary, there's nothing wrong with throwing next.js inside a container. That's how all other apps and frameworks work everywhere. It's just that vercel does some additional CDN optimization out of the box. Which is not a big deal for 99% of use cases.
First two minutes of his response was enlightening. If you choose to solve challenges at the infra level. It's a lock in
I still can't believe we have normalized seeing preloaders again thanks to JS frameworks.
If NextJS is so hard to host, then either the framework is a complete dumpster fire, *or* it's designed for the complexity needed by the 0.0001% of websites. (e.g. pre-render page fragments via CDN !?) So glad I don't have to deal with this.
Finally someone who isn’t a cult member of any particular tech. “Just use what you need” if it’s production absolutely right. I’ve not needed to touch next for anything other than hearing people rave about it, I didn’t like it. I don’t like not being able to know what’s going on. A docker container for a website is like a Wi-Fi connected fridge. SSR will destroy companies.
leerob (Lee Robinson) recently posted a self-hosting nextjs tutorial on his channel. It's a good video for anyone that wants to learn the basics of self-host even if you don't use next.
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
The timing of this video is interesting. Lee Robinson (the VP of product at Vercel) just uploaded a great tutorial on how to self-host Next.
I love how this channel doesn't pay lip service to Vercel & the likes but instead focuses on the freedom of technology. I'm not even a professional programmer, but I enjoy this very much.
Love that framing of the capability from owning a deployment platform and being able to use two ways to solve the problems
In other news, Rails is literally optimized to work out of the box for a single developer
15:45 In summary, there's nothing wrong with throwing next.js inside a container. That's how all other apps and frameworks work everywhere. It's just that vercel does some additional CDN optimization out of the box. Which is not a big deal for 99% of use cases.
First two minutes of his response was enlightening. If you choose to solve challenges at the infra level. It's a lock in
I still can't believe we have normalized seeing preloaders again thanks to JS frameworks.
If NextJS is so hard to host, then either the framework is a complete dumpster fire, *or* it's designed for the complexity needed by the 0.0001% of websites. (e.g. pre-render page fragments via CDN !?) So glad I don't have to deal with this.
Finally someone who isn’t a cult member of any particular tech. “Just use what you need” if it’s production absolutely right. I’ve not needed to touch next for anything other than hearing people rave about it, I didn’t like it. I don’t like not being able to know what’s going on. A docker container for a website is like a Wi-Fi connected fridge. SSR will destroy companies.
leerob (Lee Robinson) recently posted a self-hosting nextjs tutorial on his channel. It's a good video for anyone that wants to learn the basics of self-host even if you don't use next.