EVERYONE NEEDS TO WATCH THIS! History keeps repeating itself! Notice how we keep hearing about 5 times it improved something but didn’t work on a large website. The test of a great pattern or architecture is if it was done everywhere does it still work well and is easy to maintain? Yes and it is good, no finds areas of improvement

React is fixing the wrong problem. With fast 10ms to 25ms api calls that can run in parallel, the new concurrent features aren’t needed. Need to move away from Microservices to modules and significantly reduce call tree size which is the root cause of latency. Microservices were created at a time of limited memory and slow spinning hard drives. This isn’t the case any more and the microservices aspect of systems needs optimized, not React.

Words actually mean something?

"All (if not many) declarative code has some sort of underlying imperative implementation" this might be best statement to differentiate imperative and declarative paradigms.

Can you please make content on micro frontend as well.

I got deeply annoyed just by seeing the pop ups .... lol

Sooo good!

Rad video! 2 points of contention though. Flash was created by MacroMedia, which Adobe purchased. Flash was not killed by Apple's iPhone, tho Flash was grueling on battery life. THE BIG problem with Flash was that it offered ZERO SEO. All the biggest companies paid to make "interactive" Flash sites. And when their SEO disappeared, they paid top dollar again to for HTML/CSS/JQuery to compete for SEO agian. Also, Flash sites couldn't be scrolled and took ages to load. Flash was cool, but doomed all along. Much respect! Awesome work!

Why are you using JavaScript??? YUCK!!!

Wow. No amount of pausong has allowed me to understand this video. Now I'm just scared of JavaScript. I wasn't before.

Svelte and SvelteKit will be the breakthrough.

It seems to me that the main problem in this hypothetical scenario is that you are needlessly requested to make an abstraction for 7 lines of extremely simple code :P Maybe this is why I am not a project manager or lead dev, but it seems like those 7 lines of extremely simple code solve all 4 of the issues you laid out that were created by the abstraction in the first place.

I am trying dsa leetcode in java ,so as a beginner should I focus more on imperative or declarative approach to solve problems ?

i still hate react just because its made by facebook, vue or svelte is the way to go

For idiots who code in notepad

So basically declarative is imperative abstracted away so the average programer doesn't need to know how stuff works only the outcome of it. I guess this approach allows faster development and readable code but it also can lead to badly optimised, buggy and resource intensive code due to devs not understanding why something works the way it does and what are the pitfalls of certain abstractions. My first instinct is comparison in C# between a classic foreach loop and List collection list.ForEach( => ) that is basically a while loop surrounded by two checks that throw exceptions. Due to those checks the list.ForEach is slower and more resource hungry then a classic foreach (with each new edition this gap is narrowing due to optimisatios) but both have their use cases especially if not using something like a Result pattern and assuring that the classic foreach will ALWAYS get some sort of collection so it doesn't crash the program due to null reference exception.

I complained a lot when Hooks was introduced. Now I have some clue why thing is what it is now.

Borer Orchard

the explanation was great

Okuneva Neck

And here I am still using a custom backend like flask for APIs and using next.js as a frontend tool 😅 how can one build web applications in next.js that interacts with cloud or databases?

Sometimes it is just easier to use HTMX. And this is one of those times.

Was getting into so much spaghetti code with use effect+ use state , useState causing rerenders of the component and retrigerring the useEffect until someone reviewed my code and just told me to stop using useEffect for simple data fetching (which i was using it for). So after a bit of searchit i ended up running into react Query which is not only better ,but simplified my entire code

react and npm also requieres a lot of bullshit on his own, plain web components with a template are very economical on his own

What a great video!

best explanation btw

Is this still relevant? Is Next JS still the best framework to build web apps today?

that was a really nice video thank you, please what is the name of the theme in 5:40 ?

I should probably give this a good, I've always abstracted API calls to a API client directory - then I call them in a Zustand action.

Really love this under-the-hood insight. Thank you

But have you ever tried sveltekit?

I lovefllow searies hearing evaluation always

something that was initially a sidekick has replaced it's successor at many places

Do you have Qwik. Made from Misko Hevery. You know him

RQ is good, though I prefer SWR.

damn cool Explanation☸☸

How about indexdb 😂

Vs rtk?

Why the fuck is everybody put into even smallest projects its so much overhead layer TF is wrong with all of you.

I still don't understand: Why build a bespoke DB for a web framework, especially for content sites (and not "Facebook"-kind of sites 1:00) ?

the Theranos biggest scam girl lmao

Thank you

Thanks for this!

Best next.js intro video I've ever seen!

In Angular, the team have added signals, because people would not learn rxjs, but the thing is, when you actually take the time to learn declarative rxjs Angular, you find it is one of the best things you've ever learnt in programming, and you want to use it all the time. So my strong advice would be to invest time into it. It is far superior to imperative (in Angular at least).

Story of SvelteKit when

How about other react-query alternatives?

I’m a c++/GoLang backend dev and never touched web stuff. Trying to start with no knowledge of any frameworks was wild so I decided to roll a small one of my own to learn how they work. Now I’m here, and I’m stoked about nextjs

Make a The Story of Nuxt 3 video also

Fred's audio was a little unclear