Theo Browne: Next.js is a backend framework

[CoryTheSimmons]

The presenter is pretty good at this kind of stuff. He should start streaming.

[al]

Cool video. Learned some interesting points about where Next can be tricky. I look forward to explore your suggestions!

[andydataguy]

Haven't watched Theo's videos in awhile. Glad to see his face! Will have to get back into binging his streams

[mozahid]

Thanks, working on my first next.js app and I was going to try and use it it with rails as a backend. But it seems like it meets the criteria for just going serverless! So excited to test this out.

[mostlydevs]

Thank you theo. The explanation is pretty great.

[zombiefacesupreme]

It's hard to argue against this with the full implementation of server components.

[abenjamin]

NextJS was just described to me the other day as a “Fullstack” framework

[remyvanlis]

Yesterday, I created a fresh nextjs 13 app for the sole purpose of back end stuff. It's actually going to be a REST API and I'm probably going to cry a lot, but it's just because I have to deliver this to someone who doesn't deserve a good backend. Sad to hear it's actually a backend framework now.

[domistry]

Thanks for sharing Theo, would like to see some pairing with Next JS as an example of a complete full stack experience!

[DominikSipowicz]

Great video Theo. TIL S3 presigned URL!

[raygan]

Using presigned url does might be dangerous if a malicious user will spam your bucket with many large files, as you cant validate the file size

[yogeshdharya]

Can somebody tell me the BGM being played at the beginning . I was legit vibing to that . By the way i've always seen that people using react slowly shift to nextjs in the long run . Quite evident now

[Miguelmigs]

It took me so long to realize this. I wish this video was uploaded like a year ago

[sungjuyea]

Is it correct to understand, that react/nextjs is now also backend frameworks, that they're now doing stuffs what rails or django(or maybe spring) has been doing over the past decades? But then, I wonder, why do we need to use React rather than rails or django? I think there would be tons of issues - like db security, db configs, ORM, managing session/cookie, etc., which are relatively easy to be "ignored" on the frontend side.

[johngagon]

Front end has always been a somewhat ambiguous term. Thanks in particular for that bit. It can mean the browser client/local storage, cookies etc. as well as the code/files set apart to communicate with it. This is clearer to those I'm training after having watched the "create react app - why its bad" video. While technically on the server-side, it isn't meant for all the other backend stuff that node comes with. Helps to understand some of the contracts or boundaries between each piece. The browser's "contract" to not share too much of the end user's OS and also the server's need to protect its own OS by keeping isolated from its high value assets like data and secured files.

BTW, I am not sure exactly what "the edge" is or how to explain that. Seems like a new term for something else I know / could easily figure out but still a very overloaded newish term.

[brunomello]

Can we have different requests based on method in the same path now?

For example GET /books and POST/books doing different things

Last time I was learning next this was not possible without doing some ugly stuff like "if method === GET then".

Is there a more pretty solution to this problem today?

[aaaaanh]

I'd ponder this YouTuber might find success on Twitch doing live coding stuff and hot takes

[brunomello]

At what point should I ditch the "old school pattern" of having a separate backend (nodejs express app that provides json API routes) and a frontend (react with create-react-app or nextjs) in favour of "joining" these two in a single application (nextjs with API routes)

This might be a dumb question, but isn't this approach mixing the concerns instead of separating them? Before you had an application that only worries about backend stuff and an application that only worries about frontend stuff, and now you have these two things that used to be completely separate mixed in a single code base. This seems counter productive?

[malinaeemi]

It is a backend framework, but for something like hackathon or small workshop or proof-of-concept applications. This is exciting!
However, for anything remotely serious, who are we kidding?

[chrishamilton]

7:40 is this true that the serverless function will die after responding? Doesn't it have to wait for the function to return? Why wouldn't you be able to execute code after returning a response?