My Weird Journey To Next.js 

and i fell in love fast

@@angularfireman5895 and hard

not with Go

Lmao

Where did his vows for being faithful went?

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.

Same 💀💀💀

Nice username

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

Theo's entire channel is an ad.

For real

nah

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

I looked for a comment mentioning the lazer flip :D

"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 !

Same here, I'm hosting multiple projects from Next 13 to 15 on a VPS and it's all fine and running

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.

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...

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

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.

Good catch! :)

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 ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-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

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.

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.

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

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".

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

give it after things get settled a bit. by the end of this year

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

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.

Yeah, the guy who just explained in this video how his very first RU-vid 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

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.