I built the same app with 5 different stacks
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
I’m done.
Theo - t3․gg
185.8k views
The Different Candidates for Dark Matter, with Katherine Freese
StarTalk
35.6k views
My new app is really stupid (I wrote none of the code)
Theo - t3․gg
58.4k views
How I code with AI right now
Theo - t3․gg
192.1k views
Giannis Is DONE With The Milwaukee Bucks!!
The Arena
160.1k views
AI sucks at art still
Theo - t3․gg
41.7k views
GPT-5.1 is built for normies
Theo - t3․gg
67.0k views
I Let 3 AIs Compete to Build the Same App…
Tech With Tim
4.3m views
Breaking down my current tech stack
Theo - t3․gg
104.3k views
The current state of gpt-5
Theo - t3․gg
61.5k views
Top Comments (10)
Please make Open Source Github repo, so we can add our versions with another stack, or improve your versions. I really wanna show how Rust + Htmx version would be fast
The NextJS implementation contains so much implicit knowledge you need to keep in your head to understand how all this "easy" "baked in" stuff works behind the scenes. Yes on something like elixir you have more lines of code but once you understand the mvc pattern it stays the same and does not change all the time. You can move around and understand the code base without knowing how all the cache & await connection etc. works. Nevermind the fact that in Next all of this implicit knowledge changes every two months
If I have a look at some of the comments, this video kind of drives home Prime's point about DX just being familiarity with the tools/language/... I'm not saying the niceties in Next aren't real, but the other stacks most definitely include features that would improve performance or "DX", but weren't used in this video because of lack of knowledge. The "number of files"-benchmark also just indicates a style difference. Splitting a project with a given number of lines over 10 or 20 files just moves the balance from searching within a file to searching for a file. With proper naming conventions and editor support, there's something to be said about both approaches. Very nice vdeo though, on a more global level this clearly indicated the pros and cons of not only the stacks themselves, but of the technology choices. You could sub rails for laravel, go for rust, next for nuxt and come to very similar conclusions because the "approach" is the same.
Actually, you can use Turbo Frames to do the experience in a single request in the Rails version
Calling Go an old stack. You're under arrest.
As a Brazilian and a José, you NAILED the pronunciation at 17:33
I think its pretty clear that you don't just introduce graphql into your project to make an SPA with 2 images and buttons.
wow that elixir app demo was such nice to look at. its so smooth and fast when compared to nextjs demo for some reason. Need to try it manually.
You could have done something very similar to your Next cache in the Elixir version, by using a GenServer or an ETS table. I've found that Elixir/Phoenix projects can go crazy far w/o a database thanks to the OTP primitives.
I really appreciate videos like this. Great to see your takes on these frameworks with a bit deeper understanding of some of the gripes, along with the things they get right
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)
Please make Open Source Github repo, so we can add our versions with another stack, or improve your versions. I really wanna show how Rust + Htmx version would be fast
The NextJS implementation contains so much implicit knowledge you need to keep in your head to understand how all this "easy" "baked in" stuff works behind the scenes. Yes on something like elixir you have more lines of code but once you understand the mvc pattern it stays the same and does not change all the time. You can move around and understand the code base without knowing how all the cache & await connection etc. works. Nevermind the fact that in Next all of this implicit knowledge changes every two months
If I have a look at some of the comments, this video kind of drives home Prime's point about DX just being familiarity with the tools/language/... I'm not saying the niceties in Next aren't real, but the other stacks most definitely include features that would improve performance or "DX", but weren't used in this video because of lack of knowledge. The "number of files"-benchmark also just indicates a style difference. Splitting a project with a given number of lines over 10 or 20 files just moves the balance from searching within a file to searching for a file. With proper naming conventions and editor support, there's something to be said about both approaches. Very nice vdeo though, on a more global level this clearly indicated the pros and cons of not only the stacks themselves, but of the technology choices. You could sub rails for laravel, go for rust, next for nuxt and come to very similar conclusions because the "approach" is the same.
Actually, you can use Turbo Frames to do the experience in a single request in the Rails version
Calling Go an old stack. You're under arrest.
As a Brazilian and a José, you NAILED the pronunciation at 17:33
I think its pretty clear that you don't just introduce graphql into your project to make an SPA with 2 images and buttons.
wow that elixir app demo was such nice to look at. its so smooth and fast when compared to nextjs demo for some reason. Need to try it manually.
You could have done something very similar to your Next cache in the Elixir version, by using a GenServer or an ETS table. I've found that Elixir/Phoenix projects can go crazy far w/o a database thanks to the OTP primitives.
I really appreciate videos like this. Great to see your takes on these frameworks with a bit deeper understanding of some of the gripes, along with the things they get right