What Theo Won't Tell You About Next.js

preview_player
Показать описание
But should you? Let's figure that out.

Рекомендации по теме
Комментарии
Автор

I love what's starting to happen on YT with all of these serious discussions about dev. Love seeing different perspectives, because we all learn from it. Fucking banger content, thank you.

_sjoe
Автор

"ISR whatever that is, I am too dumb to figure that out"

Thats too relatable

wlockuz
Автор

Sounds like a real backend developer busted some myths. However I think for us that use NextJS heavily we’re not full fledged backend devs. We’re mostly front end, need reliance on server side rendering of react components while needing a few backend API calls.

thedigitalceo
Автор

The chopsticks were so out of left field from what I expected 😂 instant subscribe

Jdunn-vu
Автор

This, is FANTASTIC. That model of web project structure is spot on and so versatile, and you seem so sincere/authentic/honest with all your statements. So satisfying to watch

kangalio
Автор

Absolutely brilliant content, keep up the good work! 🙌🏻

aldomeza-dev
Автор

Makes sense. I just finished working on a organisations finance and management project. Even though Next has a clean and robust workflow for the front end but alot of the backend implementations required a dedicated backend framework. For example run cron schedule jobs (generate automated reports on daily, weekly, fortnightly mornth quarterly and yearly bases). Mailing service so send out alerts, reminders and warnings, server health checks, file system related tasks, db service layering (caching, index metering and optimisation) etc. These things could have some how been managed with next but would have absolutely been inefficient and not very flexible.

ammaraateeb
Автор

My friend this is an amazing video.

Nextjs is growing up so much! Thanks to Theo also.

codewithguillaume
Автор

Great content . Goes to show how thoroughly we need to think before developing software .

Beny
Автор

Not sure why you would need to constraint yourself to nextjs in this case for backend if it's limiting your project. Just create the Frontend in nextjs and
use what ever you want as backend (rails, nest, python, java, c#) it doens't matter

for example: there are a lot of AI tools in python why would you need to force it in JS (nextjs), use flask or any other BE available and consume that service from the FE.

arkngelus
Автор

Awesome lessons with great visual example that really helps with following the content. You put what I have been thinking about in such great wording and figures.

Nextjs is good if you have a simple backend to support the main thing that is your frontend, but if complexity is in the equation, you are better off using more dedicated tools. Nextjs is full-stack yes/maybe, but an unbalanced full-stack, like how Django focuses more on the backend, and only gives limited frontend options through templating

baohuynh
Автор

Wow, what a great explanation of all the components of an app. Please more of these :)

rickr
Автор

This was good. I hadn’t put that much thought into backend from NextJS vs other platforms. My apps have been more simplistic applications that do more front end work so NextJS has worked pretty well for me. But if I was doing something that didn’t have front end in there I wouldn’t be using NextJS but doing something else that handles just back end and handles it very well.

This was good, thanks for sharing this. :D

sockeyes
Автор

Immediately subscribed, very clear concepts 💯

fahimmuntasirniloy
Автор

Makes sense! Good visuals and insightful content

al
Автор

I like where this was going but it ended abruptly :). I’d love to hear more about the frameworks that are allowing you to do the side effect work ergonomically. In the past, I’ve done one of 3 things:
1. Early on or when it’s likely there will only ever be a few events, use a simple background job / delayed job system (resque, beanstalk, etc)
2. When there is a rich set of transformations or systems concerned with events: a fancy message bus / durable queue (kafka, MySQL magic, etc)
3. My favorite: when you don’t care about delivery guarantees - UDP! (StatsD ;))

efkastner
Автор

Thank you for this explanation … what would you recommend for a beginner working on an e-commerce website + mobile app ?

fereydounomar
Автор

This is great, I really learned something from this video.

EldorJ
Автор

Good point. What I do is that i don’t deploy on vercel (since lambda stop after responding) but I deploy on google appengine instead. I wrote many “fire and forget” functions. That’s not ideal but that’s the price I’m willing to pay for using the amazing t3-stack lol

foreach
Автор

Hey mate, that was a great video, but could you please clarify on the mental model for the stateful early return with other side effects being processed after

Sanjay-hzrz