Purchased! Can't wait to get started.

Is this nextjs course with latest updates? Like next13

like the miniature of the video

Take my money 💸

Any chance Nuxt3 course happens? And/or sveltekit. Good stuff though.

What’s updog

@@invinciblemode not much, sup?

It's not a smart choice, it would have been if the node ecosystem wasn't a mess and if there were better frameworks for it, a lot of people thus don't want to write their backend code in JavaScript and that's understandable. (Big) Companies would never use NextJS for the backend of a serious and not very small application.

@@heroe1486 The reason I think it’s smart is that you can make a website without php but you cannot make a website without javascript. Of course I refer to today’s standards and php can be replaced with any other language in this context. I’m also not a huge fan of node and don’t enjoy backend scripting that much. But apparently things are going to evolve around this approach.

Full stack is indeed a future. Businesses will not be paying specialists anymore, they will expect us to be able to deliver apps from UX to deployment. But that obviously has it''s cons. Knowing a little bit of everything means we will not be excelling in anything which can lead to overall lesser quality. Of course, talking about simple to medium projects. Big and complex projects with uber business logic will always require specialists and domain experts.

When tooling being upgrading year after year, frameworks, ai, etc. Frontend developers will convert to Fullstack developers, and Backend developers only be necessary in a microservice arquitcture or big apps, no need in small apps.

@@timebroua that's why backend developers will be not removed. Frontend developers will transition to fullstack and backend developers will be needed to be more expert. As backend developer, you really want to create the endpoints for a frontend developer? and then argue with him because comuncation problems?

same

when using a server action in a client component, does the action still happen on the server side?

yes@@alulaleak

+1

Remember we were all using Next because "it's just React but with extra goodness (file based routing, handy utility functions, middleware etc)"

I feel like using react query its more easier, readable and intuitive, and can be used outside of html forms

​@@Gogonel290 All of that without needing to couple your backend code with your frontend one and not being forced to use Node, React Query makes everything very easy. And as a bonus it also works with Vue Svelte and Solid

Same

agreed

I think next is unnecessarily more complex in terms of syntax. Doesnt seem that scalable now... Ror on the other hand is easy to understand...

I see now why most of the elder devs that were really successful were RoR devs (in my region at least)

@@_sevelin you're talking about scalability, almost all companies that used ruby on rails migrated away from it because it was dogshit slow

@@marusdod3685 i meant the code's scalability (i think the better word would be maintainability). i can't imagine writing so much non relevant code to achieve something simple. at least that's where ror shines...

it's a new thing in React, which is what Next is meant for. you are acting like they claimed to build a new base on the moon or something

Stop trying to sell us your shitty boomer frameworks

​​​​​​​​@@YuriG03042 It's in response to the Abramov's "With PHP you have to reload" And welll yes that's what they're trying to convey, just look at their Apple like conferences and overall marketing for things that have been here in other frameworks/PAAS for years, same for the "it's going to reshape the industry" kind of reactions from the public.

Also same stuff exists in SvelteKit for quite a while

​@@buldezir And apparently in Remix too

Yeah and it worked like a charm...no page reload!

Dam I didn’t even realise this was AI generated voice?

@@yellowboat8773 yeah it’s especially funny during the jokes because AI can’t get the cadence quite right.

for non-native english speakers, it's far too fast

exactly

In practice "move your app to a different backend" will almost certainly involve a lot more than simply changing a url. Many frontends are typically strongly coupled to a particular backend and vice versa with the backend only existing for that frontend, and the argument is that in many cases having additional abstraction around this coupling can make us less flexible rather than more. React has always been bullish on removing barriers between code and challenging theory about how we should divide things up, remember "separation of concerns not separation of technology" so this is par for the course for them. Of course if you feel you do need that abstraction and explicit separation you are still welcome to write APIs and separate client side UI. But if that UI is the only consumer of that API then this may be a decent way to create it that's clearer, less complex and more performant. What's more if you further down the line realise you need the API then the pathway to going from server side to API led is probably a lot smoother than it was.

How often do you do that though? I'd say for most indie projects that's not a big concern

It's Laravel without reload

but you will never, it will never happen :)

Its similar to developing in Ruby On Rails framework.

Was wondering just the same, especially if they are identical, which I suppose they are.

​@@amatzen in that case the are probably served from the browser cache

​@@gaborkrisko They are not served from cache, because there's a different ?v=123123 on each of them, each time they load. But maybe it's due to the development/local server and how it ensures that files are always fresh?

Just the Dev server, wouldn't happen in prod

yeah, next13 is entirely "inspired" by remix - and likewise the new routing system in remix v2 is inspired by nextjs13 - its a win win for all frameworks.

React router dom v6 has it too?

@@ianbdb7686 it's not new and in react. Got a long time in remix

Refetching everything is usually and actually a very good thing as you won't need to engineer complex situations. But, as far I understood in this situation, it will only refetch the specific component.

Impossible, that's not the same audience, most or their users are beginners or small companies that benefit from it for pennies before scaling a bit (and realizing the pricing isn't worth). But yeah the hype isn't deserved, it's overpriced (40x the price of a VPS or CDN for bandwidth) because most people can't figure out docker, how to use a CDN and GitHub actions and think they're doing crazy stuff that no one can reproduce.

Their pricing is obnoxious.

@@heroe1486 I mean, every 3rd party service operates like that. It abstracts all of this stuff to be few clicks as possible so it's convenient. You are paying for the convenience, that's mostly it.

​@@heroe1486 on your point about the vps and cdn being cheaper, if I'm making a portfolio site or just want something quick and usable, I don't wanna go through all those steps. for a production project, yes it makes sense to have more fine tuned control in order to solve those issues but for a personal/hobby project not worth the extra hassle (which leads to effort invested that may demotivate me from finishing the project in the first place). Theres still even an argument that that overhead is worth it: sure you'll save money on deployment but you instead pay more on labor/knowledge cost.

😂

that's what we call vendor locking

Middleware

You can use pretty much any authentication package you want? All you are doing is either decoding a JWT or doing a session cookie lookup.

yes, but why?!

Look what they have to do to mimic a small portion of our power

it's not 2017 anymore

@@axelramirezludewig306 yeah it's 2001

Ill say this. As a maintainer of an OSS library using SWR, server actions completely decimated its use case in web. For RN, and non next apps SWR is still useful, but in next 13 it’s completely useless. I almost discourage using SWR in next 13 app dir.

server actions can be defined inside components, imported from other files or passed as props. This is not the same DX as using SWR or react-query.

from "next/navigation"

It wouldn’t work. Because the functions like and dislike are actually server functions

it is but you have to redeclare it when the function is in client component file otherwise the function will be a client one

I think same as you, but looks like people don’t care and are just hyped