My Weird Journey To Next.js
HTML-код
- Опубликовано: 19 июн 2024
- I got to Next.js later than most would think, and I dragged my feet for AWHILE. I think my path from backend to CRA to Snowpack to Vite to Next.js might help y'all better understand WHY I like Next so much :)
Check out my Twitch, Twitter, Discord more at t3.gg
S/O Ph4se0n3 for the awesome edit 🙏 
Наука
You fall in love a lot
and i fell in love fast
@@angularfireman5895 and hard
not with Go
Lmao
Where did his vows for being faithful went?
My notification for this video cut off in an interesting way: "Why I used to hate N..". I was like, ayo?
Same 💀💀💀
Nice username
you're telling me we're supposed to pass all these tests, know all these frameworks, all these languages..
AND THIS GUY GETS HIRED AT TWITCH CAUSE HE LISTENS TO BANGER MUSIC???
okay theo. slightly jealous.
All throughout human history the story is the same, it is not WHAT you know, but WHO you know. It will always be safer to hire a person that you know than someone you don't, even with a better resume/test/interview/whatever.
Yes, the part about hearing the same music to get hired is hilarious :) But Theo did much code before, so a well deserved opportunity ;)
You’d be surprised how often this happens. I have never applied to a job, I just happen to know good people at companies who know other good people at other companies who need developers. So they approach me, not me approaching them, which I’m very grateful for
Make good friends in the right places
It’s not what you… oh wait, it’s been said already. I’ll just grab my coat.
If you regularly interview and move around, this is something that happens sometimes. Truth is, if you have a little bit of notoriety in the community and interview often (which Theo is a big fan of) there will be jobs that you squeak through the interview process partly on your reputation. Very common. With that being said, you should seek interview processes that test yourself. It's good for everyone, they get to know your limits and you do too, if hired expectations are set.
love hearing more about the story of how you started!
Can't relate. I used to hate Next. Years passed, hate it even more.
Why?
Same.
Explain?
I’m trying out remix. At work we use Laravel
@@PetrosTotskas poor and non-configurable server (monitoring, logging, programming cache, request hooks and so on), features vendor-lock
The beginning of this video perfectly captures how I feel. Thank you so, so much for showing me light at the end of the tunnel. I feel much better about eventually finding something I love and getting good at it. This is invaluable ❤
I came here to see something about next.js.. Now seeing the casual lazerflip, makes me want to grab my board and visit the local skatepark.
Sounds like a long ad
Theo's entire channel is an ad.
For real
I make enterprise ecommerce for large businesses on create T3 and next appdir is a godsend. The integration of caching, simplified entrypoint model and granular control over build/deploy mode make everything sooooo much easier. ❤
the inconvenient part is cost of Vercel or Netlify when you get DoSed
nah
Really enjoyed this one; i came here for nextjs and stayed for the mini dev/channel biography 🙌 i still ship SPAs with separate BE/FE but i am now curious to give this server side components stuff a try
used to love next, still have a Next sticker on my laptop. Tried to deploy a large nextjs project to AWS with AWS CDN, now I hate Next 🥰
You're awesome Theo!!! Thanks for sharing things that we wouldn't get to hear otherwise. I really learn a lot from watercooler/breakroom conversations. Weirdly enough I've learned the most from you and Bro Code's channel. You got style and class but more importantly I like how the tools you use work. My dad taught me to use the best tools to build houses. Now I code and I approach it the same way. Cheers man.
I used to love Next.js.
"But then I took an arrow to the knee" or "But that all changed when the Fire Nation attacked". Which one?
@@rikschaaf I am Melon Lord !
The t3 stack is pretty nice, but what would you use if you had to develop for private cloud? Would you run it on kubernetes in a container ( or use a webassembly runtime )? Would you use coolify or similar instead of Vercel? What auth provider would you use if it had to run in that private cluster? Would the rest of the app stay the same or are there other things that would need to change?
That nollie tre and lazer flip was insane 😮, I knew you skated, but I didn't know you were that good.
You're the first dev beside myself that I know skated seriously.
I looked for a comment mentioning the lazer flip :D
Im still confused as to whether trpc is still needed in next 14 or if it is redundant now that we have RSC and server actions
Would it still be beneficial to use it in your projects?, T3 still uses it in there templates.
Maybe a video clearing this up for users would be beneficial as Ive noticed others confusion around this.
I believe the value of tRPC is it provides you a tunnel for your client to interact with your backend with typesafe apis which is not possible with only server actions and RSC. RSC though rendered on the server doesn't make interaction with backend type safe. Things like tRPC and Hono RPC bridge that gap
We deserve a compilation of all of Theo's thumbnail faces.
people are hating, but i love next, easy to use, great doc, sure a weird caching but as far as i know thats it, and im not hosting on vercel
Same here, I'm hosting multiple projects from Next 13 to 15 on a VPS and it's all fine and running
cool to hear the evolution, theo!
Does somebody know why router.refresh() reset scroll for previous page?
How do you make them move over is my question??? I’m still constantly fighting about why Tailwind isn’t the devil to no avail. 😢
Genuine question, folks having issues with next caching, can you describe the scenarios or examples and how did you manage to overcome it?
I only just started using next and vercel like 2 days ago, still in the process of building incrementally, and ran into the caching instantly lol. Changed it pretty easily, but imagine my surprise when I just found out they’re changing the default caching behaviour in v15 because too many people found it unintuitive lmao
i used astro. it uses vite not webpack. why did next not go to vite too? its kinda the standard these days. so much easier to configure.
Lotta contrarian commenters here! Next is great. Whether you just use the pages/ router and export a static app, or you're taking advantage of some of the new RSC stuff, next makes things super easy ime. I have no idea what people are complainling about re: speed and resource usage - always super fast for me.
Not liking next doesnt make you a contrarian. Calling people that and being unable to even conceptualize that others have issues you don't due to different use cases makes you look real stupid though.
I used to like next js but nowadays I kinda don’t anymore. Way too much boilerplate code, over engineering and bugs you’ll have to find a way to get through. It feels like I’m using a beta kind of project, I just don’t trust it. Anyone else feels the same?
Just you
Lol literally just you - the whole point is that they decreased the amount of boilerplate insanely and simplified the system
Currently I have to use 14th version. It's complete disaster especially App Router... So much bugs and over engineering ideas...
Dude, was that a switch laser flip?! I didn't know Theo shredded!!? Rad!🤘On the topic of NextJS, used to love it. Not so much anymore. The super long dev mode compilation times with the app router are torture.
You get your mind blown a lot
3:33 Firing is good for everyone, the team gets to feel like they are trimming fat and the person fired gets to hopefully move to a better position and realize they needed the kick in the ass to get better and switch things up, which in tech typically leads to a better fit in position or more money, or both. I am a big fan of not taking firings too seriously and looking at them as opportunities. I've only been "let go" once but I've been part of layoffs that felt an aweful lot like firing. Not sure why I went on this rant, but it's good to hear.
What stands out here is your passion for webdev. Don't worry about what other people think, they just wish they were you and actually loved their lives. You just keep going because your passion, your dedication and your work ethic are something that one cannot buy. You have it or you don't. And you have it. And, yeah, Vercel should pay you more. If they don't, they are totally using you. Keep your head up And well done!!!!
How fun to hear the Theo origin story!
I had this idea to make a intraNet for my company and started messing around with next.js.I started testing random ideas, like what will happen if i do it this way or that way, or will this or that work, and i have to say that i am amazed at what next.js can do. I use next.js with mongodb and JS with no TS so i can try anything that comes to mind and the app rarely brakes.
What log drain solution do you recommend?
Vercel log drain price is outrageous, and we are exploring Axiom - but their APL is confusing.
Agree, Theo recommended Axiom multiple times, but honestly it feels like a glorified dashboard with a poor APL, not a real log warehouse. Its amazing compared to a .log file 😂 but conpared to DataDog, Dynatrace abd even Vercel’s logging, its kinda meh
since next 14(I've tried it)...it just feels void; like so much bullshit & frustating....or rather indeed skill issue
ah the angst of the common framework gluer
I'm a Go dev who also like Next and Sveltekit
Great shirt as always. I guess you are really a front end guy now
At first, I loved Next because it gave us both SSR SSG and CSR while other frameworks were focused on only one. Then they added on to it. After T3 stack, I was be able to go full stack and made great projects with it. Amazing DX. I still think pages router is still way to go for dashboard apps, since it's just React, you can put or migrate to any other project just fine, or onboard people who don't know app router but knows React at least. App router and RSC were polarizing stuff, however I think idea is great, just needs to be matured. While they can show some more love to the pages router.
nice one theo
it's funny how bad comunication because of team not working on the same timezone leads to ping pong and then to "i am just going to write another layer between frontend and backend"
Next.js is a pain in the thing if you don't want to pay vercel. I'm moving back to Nuxt and Vue since they're stable again now 😍
Remix 🙌🙌 sorry am a fanboy
@@Motion152 Remix is pretty nice, I like it far more than Next.
I don't get it, what are you using that's so hard to host NextJS outside vercel? I've been deploying NextJS on Amplify and Docker images for years now and I've never had any huge problems
@@Motion152 Huh... my reply to you got hidden/removed. All I wrote was that I think Remix is good and I like it more than Next... wonder if this one sticks.
@@davidecarvalho7077yeah, I also dockerize most my nextjs apps and host them on AWS. It seems to work fine. Vercel also has pretty great documentation on deploying apps yourself without Vercel.
Hey, aren't you paid by Vercel to advertise and influence for them?
Welcome back.
Next is good, but I'm REALLY enjoying Remix. Even trying to convince my employers to take it on.
What's up with the negativity here
Maybe because Next.js and SSR are a trap, and people are trying to warn others not to fall into this awful mix of frameworks?
@@planetchubby how is it a trap?
People have a major skill issue but are coping by convincing themselves that its NextJS fault that they can’t understand fe/be boundaries
@@claasdev I like React for the frontend, but it should stay away from the backend. That's basically the "Vercel trap"
@@MrManafon When your "skill issues" are solved, you'll see that the real problem with Next.js is how it horribly obscures those fe/be boundaries.
The anecdote about you getting your first job at twitch is inspiring. I know some people will say it's a different time and the market is forever changed, but I needed to hear that
Thanks for the history lesson. 😁
i used to love Next.js. Next now is completely broken from the caching issues to the slow dev server
On a project, each refresh (instant on my M1) takes minutes to run on the junior windows, we had to go back to pages :(
turbopack is still in beta (next build --turbo is WIP) and caching is disabled in v15
@@martinlesko1521 I hoped for v15, but then it has React 19 RC in it :/
@@AlexWerner42 react 19 rc is necessary for next 15
@@martinlesko1521 Sure, and I'm 100% of that, I keep going RC till early node v.
But here, there is junior people, on a launching project, nothing work for them, had to revert pages; It nice from Vercel, but it's a mistake somewhere. The CEO of the corp now dislike vercel, just because it means problems, he probably won't use it ever again... Vercel build a less neat path here :/
But I'm complaining of Google-behemoth not moving, so I cannot say I dislike them, just... I can't work past specific Next version from a contextual case.
Just try to get a basic requirement like a custom HTTP 500 page working with the app router in dev and production mode in the latest release version and then after failing tell me again how much you love Next.js... 😉
Works just fine, skill issue with understanding the rendering cascade…
@@MrManafon No, it doesn't. Just search the Next.js issue tracker or Stack Overflow if you don't believe me... Or show me code that works (I like to emphasize I am writing about the new app router not the old page router).
@@MrManafon It's funny how you use the "skill issue" argument, as it seems you don't fully understand the definition of the word "skill".
@@planetchubby it means that you don't fully understand the tool, and then blame it on the tool. 500 page works just fine, once you realize that there is a cascade of error pages, and you may trigger a built-in error page if your error page fails rendering, which people often mistake for "error pages work weird". This is perfectly common behaviour in backend frameworks.
@@MrManafon 500 error pages shouldn't appear in a React framework, and they should never be "perfectly common" behavior in a backend framework. That itself implies a "skill issue".
The not typesafe router sucks tho
Look at his hair progression over 2 years
The NextJs caching is completely broken and unintuitive.
It works completely different indevelopment and production and also differs between v14 and v15.
So I would take what Theo or anyone loving nextjs with a grain of salt
caching is disabled by default in v15
@@martinlesko1521 You would be amazed how it's still messed up. Kyle from WDS touched upon this and when I found this to be true too
ruclips.net/video/3RyguimNe8s/видео.htmlsi=yRfmv3vQi_lbAYQN
@@martinlesko1521 It's still behaves differently on dev and prod. Kyle from WDS touches upon this. You can look it up
Skill issue
skill issue works just fine, and exactly the same as any other backend caching system would
I am in a love-hate relationship with Next.js. I can't live without it but it also makes me want to puke from the endless updates and breaking changes. I don't think it's production grade framework because it keep pushing you to upgrade to a higher version all the time. I need stable supported version for prod...
What breaking changes are you talking about? I can think of Image and Link changes, but those were years ago
I feel the same way. Way too much updates, it only makes you feel like you’re using a beta tool, it doesn’t feel production ready! I hate that
@@nwsome use server as default
@@mmsmsy That's only breaking if you've managed to use the app router before it existed
want to use it real bad, but i work as a government contractor and the IT security people are allergic to anything running serverside.
I'm shaking the mouse and shaking the mouse, but I'm not on that computer... trying to control Theo's cursor fullscreen lol.
Wait I have an idea, what does Guillermo listen to?
Good catch! :)
I've been really digging encore ts lately.
I think most people still hate next js
Agree. You're a good entertainer.
I didn’t know twitch uses vercel
It's the opposite for me. React's config and trying to set up SSR was a nightmare back when and it made Next.js such a refreshing change since it *just worked*. However, it's now this bloated over-engineered mess that will easily eat up 4GB ram and its dev server is slow even on modern hardware. As if they couldn't outdo themselves, the app router is even worse with performance. It finally pushed me to Remix because I was convinced no alternative could possibly screw up as bad as Nextjs has. Remix is more lightweight (dev server consuming around 300MB memory) and also very snappy. Links are faster to load and it just feels like what a SPA is supposed to feel like. Much happier with web dev now
vite-pilled for real
Full-stack next apps aren't meant to be SPAs 🤷 use the right tool for what you need
this
@@charliecarrot NextJS close to being not the best SSR solution even in the React ecosystem
Is it just me or Theo reminds me of MeetKevin whom I had stopped watching.
Example that initially you don't need to be good with FrontEnd to get started as developer.👍
Maybe I should give nextjs another chance. 💔
give it after things get settled a bit. by the end of this year
For enterprise apps I would pick vite and react-router over NextJs.
I would never recommend mixing backend logics between several solutions. All backend logic should come from one source of truth.
I really appreciate your work, but as you said just now, it is not you who is preparing stuff and doing research - you've got a team now. It is not physically possible to try all that new stuff and have honest opinion within the short time, but you need to keep churning the content. So yeah, I listen to you but I don't take it seriously anymore as your personal opinion.
I felt that hate for getServerSideProps to the bone.
If someone could just write an extension to summarize Theo videos that would be good business :)
I love next but I host it elsewhere….
Next has made me absolutely love remix
I wish Next.js becomes a real framework
Can you make a video about Coolify ?
thx for 80% water in the video
I don’t understand why so many of these comments are so mean. If you don’t like Theo, don’t watch his videos. The video is just him talking about his experience of Next.js and and his development over the years. I don’t understand the hate.
Totally not sponsored by vercel
i think a lot of the online dev community in general are arrogant, know-it-all and bitter little boys, they hate everything, they're cynical of everyone, it makes them feel important
Even though Theo brags a lot, I still watch his videos for the knowledge I gain 😅
@@krishnabharadwaj4715 Mee too. Even though I desagree with some opinions (as it's healthy to do so) I learn a lot about the topics he discusses.
I still hate Next.js 😅 Then I found Nuxt and it's the bomb 💣
the politics therapy got me to subscribe. I'm healed, just a little.
I used to hate it. It's my first ReactProject. I jumped directly to Next14. Never experienced the previous versions.
I kinda loving it now.
Why would one use nextjs if their API is already written in another language? I can see completely zero reasons and a ton of disadvantages only
theo´s thumbnails are funny, i like them
bro wtf did you even try go to say that you love functional progamminf?
I use next in the last 2 years (yes, at work... And not a start up). If i update every 1-2 months the project, it barely breaks. I really dont get why people complain so much. If fighting a bit of caching quirk makes you rage so bad... Well, you are just noob, dont you think?
its to early for this im going back to bed
please add timestamp / chapters.
In many cases, I disagree with Theo's opinions. However, I don't think anyone deserves hate, imagine it's you. Just remain respectful
RIP create-react-app.
Much better than this vercel shit.
I am very disappointed by their docs, it comes nowhere close to the react docs.
Loved hearing what your evolutionary story is! 😃
Because they sponsor you?? Just because this video isn't sponsored doesn't change it
your clickbait titles are exhausting.
Why are you saying Vercel doesn't sponsor this particular video, when they do sponsor your channel? I don't think that matters. It's effectively the same.
0:58 Chris Farley raising his sunglasses moment
Oh, Theo's finally gone mad. Well, it was nice while it lasted. Let's hope his family discovers this before it's too late and gives him the help he needs.
Remix is better, next's router is insufferable.
Vercel made sure nextjs deployment is easy only on their platform
Theo tomorrow: Why NextJS is shit and Fizzbussy Framework is the JS framework everyone should use.
Yeah, the guy who just explained in this video how his very first RUclips video was about Next, and who has been using Next in the years since then, is suddenly gonna turn around and say it sucks. Makes sense to me!
I can see that lol
Someone said “when people who have power and high influence starts favouring one thing then the world becomes worst”
I honestly dont get the hate about nextjs, if you guys dont like nextjs... Just stick to react? Oh wait most of you guys hate everything and would love working with jQuery.. so just stick to that?
And the people who complain about how much it changes.. yall just dumb as hell? App dir is being constantly updated.. pages barely does. Pages is how it was before just use that if you dont want to constantly be updated on whats going on.. but then also dont complain on how frequently app dir is updated and not pages dir.
people just want to whine, it's the intenet
@@schtormm it's worse with how stuff works for frontend, with people constantly hating on each other + backend people joining it.. it really hurts certain technologies.
The docs push Next as the primary solution and starter to a React App. Stop living in your fantasy. "yall just dumb as hell?" You're out of your depth here.
@@e_tas_ docs can say whatever it wants, as if most even read the entirety of the docs? Also nobody is forcing you to use it.. so why hate it? Also if you mean the react docs.. it also mentions to use remix so I dont see your point here.
@@arinjii5745 Tone down the emotionality for a second. Most people wouldn't complain about NextJS if it wasn't pushed so hard, if it wasn't backed by Vercel then it would likely die in obscurity or adoption of alternatives. Nobody is complaining about Waku or Remix. When it's pushed to the mainstream forefront then companies will use it, and I use Next 14 for the app I'm currently using but I wouldn't want to use it at a job. And if it's recommended as the primary option for starting an app in React, why *wouldn't* people use it? If anything most people will use it because they feel they should, because they're TOLD they should, and have inevitable frustrations as it's a half baked framework. Now stop crying like a girl.
you fall in love quite a time
No way you're not being paid to glaze next.js every video here and there
No.