Soon to come in NodeJS/Golang : "new trend to offload the server by moving some code over to the frontend; the backend is doing too much, server costs have gone up, something had to be done"
Doesn't really sound good to me to do SSR. A thousand devices can handle the processing, or the server can do that fir a thousand devices, so yeah. Your server and cloud computing costs will go up.
Your remix course from Udemy is brilliant. Having taken almost all remix tutorials available, I can safely say the approach you have taken in the deepdive section to drill down the concepts is one of the best! Look forward to more Remix content from you
i used to hate react and always choose vue / svelte over it, this guy is the reason i switch to remix because of his explanation and remix got what i need (still hated react rules though, but remix offer more goods than bads for me), glad I met Maximillian and his Remix course on Udemy
:D :D :D Year n: Just make everything simple, render everything on server and give it to them Year n+3: Okay, the users need more interactivity, move things over to the client Year n+6: We are duplicating a lot of code, let's move everything to the client, go serverless and just use it as an API Year n+9: Okay, the client side things are getting heavy move some things back to the server > Repeat...
Love your videos, Max. Random but whilst I'm here, your React and React Native courses literally changed my life. Now working full-time as a developer. Your Udemy courses made this possible. Thank you 🙌
This inspired me to rewatch your NextJS course. I never finished it because I didn't like the idea to mix backend and frontend in the same project, but now it makes more sense. Plus I don't have to use two different technologies like React for fronend and NestJs/ExpressJS/PHP for the backend.
React js is a blasphemy for JavaScript community. React nonsense must be banned across world plane. This f library makes web development unnecessarily complicated. Angular is far better than svelte and react nonsense., because it leverages rxjs subscription, angular service make communication between sibling components much easier, developers know what exactly is happening. Svelte and react have confusing code. Developer experience matters.
@avfr Ohhhh I see I see. Yeah it really depends what you need, but if that's the limitation it might cause you issues in the long run since you don't necessarily know at the moment that you might need those features in the future.
Great summary, interesting even for non React developer! Could we expect similar videos for different frameworks? I think it would be amazing to hear your thoughts about current state of Vue or Svelte!
Current state of Vue: awesome. Major players in ecosystem finally updated to Vue 3 (Nuxt 3, Vuetify). Evan and the Vue team will be improving Vue 3 1st half of 2023, then work on Vue Vapor (Vue using SolidJS tech for even smaller size and faster performance) in the 2nd half 2023. So, Vue is not bleeding edge tech like Solid JS, but it is far far more mature than Solid and Svelte as well. React is very heavy in comparison, much more complicated, though Next/Remix/et al. are working to simplify. I think 2023 is going to be a marked incline in Vue usage as Vue 2 gets phased out and folks start seeing how all-around great Vue 3 is. I'm looking into Astro with Vue for one of my projects, as Astro 2.0 just came out, meaning it's pretty decently mature, and I think Astro plays better with game engines/frameworks since it stays closer to HTML than Vue, which is off in SPA/JS-la-la-land ;).
It would be great to see update of PWA course. There isn't much up-to-date materials to get familiar with this topic so it would be great if you provide it.
@@mohamedatef2383 It's a fake name. Are you a fan of Top Gear? I've watched all seasons of old version of Top Gear, and of course The Grand Tour. I'm also looking for 2 season of Clarson's Farm. And you?
There are people saying that the significance of the changes between between Next 12 and 13 make Next 12 courses obsolete at this point. What do you guys think? I just finished a React course and had planned to start learning Next soon. Should I study Next 13 even though it's still experimental? Or should I study something else on my list while I wait to see how things play out with Next 13?
hello,Mr max.thanks for your course.i've learned js almostly one and half years.but I'm still in a primary level.and your course help me understand some basic concept knowledge.you're always sophisticated and skilled.your idea also inspired me.i really appreciated your guidance.And i hope you make a course of Vue 3 . thanks a lot Mr Max.
Thanks, this really summed it all up nicely. It's funny that we're going full-circle in web development, back to the server. When I started, we built business apps in PHP, ASP, .NET, Java, etc. that were server-side monoliths, performed quite well for a decent user load, and were many times easier to build/maintain than a modern microservices arch w/ a React front-end, for example. You could actually be an *expert*, in-depth full-stack developer and reasonably keep up with changes and updates. Let's be real - we're not all Facebook and Amazon...most of us are seriously over-engineering solutions. It was a simpler time...ahhh...Pepperidge Farms remembers!
I am sorry but I have to disagree on this. Before even with PHP you still had to write your frontend in JS and unless it was a really basic app, with barely any interaction, you had to add something such as jQuery (or manipulate the DOM directly). Further I always found PHP far tor verbose as a language, although of course this is a personal opinion. Now though, with something like NextJs I can write a full app which fetched and render data, sneak in some animations as well, some nice styling, and good performances in just a couple of days, while before it would have took me at least a couple of week. Further I can deploy my app, for free, with no configuration needed in something like Netlify or Vercel. So while I agree that JS is kind of going back to some of the PHP principles, I also believe it is doing so in a much simpler and more efficient way.
@@_scrapbookers_ Not true. I was writing highly-interactive web apps between 1998 and 2012, that used hardly any JS on the front-end. Just because you're rendering on the server doesn't mean the app isn't "highly interactive", it just means that pages refresh more often. Nothing about the current state of full-stack development is simpler than it was, in those days, in my opinion. I'm not a fan of PHP, personally, and would have chosen any of the other technologies I mentioned, over them. Was just an example of the concept, wasn't opining on the language itself.
@@VincentJenks Yes of course you could do that, but refreshing pages every so often is not the best user experience IMO, particularly when users are connected to slow networks, as the website feel very slow. I agree that often people tend to over engineer solution, but I also believe that today, with framework such as React & Next, coupled with something like Tailwind, you can write a beautiful looking, responsive, highly interactive and SEO optimised app, in under a couple of days. I guess it always comes down to what technology someone is most familiar with. I would certainly feel much more confident, and therefore develop much faster using a JS/TS stack, rather than relying on PHP.
@@_scrapbookers_ I understand all that, and that's how I build apps today - you're preaching to the choir a bit. Never was I advocating for an old school server-side approach or recommending PHP. My original point was - the frontend has become a pig and there are frameworks on top of frameworks, and just too much engineering happening, across the stack. The front-end having server-side access is a good thing and may help.
excellent summary. The only thing is that even though Hooks is a standard, most of the examples are still created using classes. I don't know why people keep doing it, although maybe I'm just lucky with the search results))
One question I rarely see addressed in these discussions of moving computation back to the server - isn't that expensive? If your app scales to a million users, or even more, and most of the work is done client side, there's no/little extra cost to host it. But now using a framework like remix, even with caching, there's going to be more and more computation on the server as you get more users and that costs more. As you mention in the video that's not a problem for big companies like Facebook but the whole point of these improvements is to make this easier for small teams, right? A surprise $100k AWS fee because your app went viral, or getting cut off by Vercel at exactly the point where you're getting popular is a problem. Doing most of the work client side prevents this problem. Until I see this issue clearly and directly addressed I'm going to stick with the old way. I've chosen not to use Remix for this reason.
I'm currently looking for my next role as a senior developer and, what I'm noticing, particularly here in the UK anyway, is that a lot of jobs seem to be going Angular! Anyway, I'm far too old to play the "tech flavour of the month!" game! I'm already heavily invested in React, and I'm already thinly stretched as a full stack dev trying to keep up with an increasingly relentless backend too! One cannot learn it all! So it's React or bust for me! At least on the frontend anyway!
i don't use reactjs anymore. i use Nextjs, typescript, tailwindcss, zustand + react-query, trpc or prisma, auth0 and stripe + cloudinary. these stacks is really good for ReactJs developers. almost anything you can build with front-end heavy applicatons.
SPA first frameworks were a huge error. After that error everyone is now migrating to SSR frameworks like Nextjs or Remix. We should have started with SSR first and gradually migrate to more and more SPA when possible.
React js is a blasphemy for JavaScript community. React nonsense must be banned across world plane. This f library makes web development unnecessarily complicated. Angular is far better than svelte and react nonsense., because it leverages rxjs subscription, angular service make communication between sibling components much easier, developers know what exactly is happening. Svelte and react have confusing code. Developer experience matters.
Firstly, they invented a complicated reactJS library that included too sophisticated Redux and children components which should be protected by 'useMemo' and 'useCallback' hooks in order to avoid unnecessary re-renders and what we see now: they suggest more experiments?! Why? To make our development easier?! Honestly, I do not understand why you love this library...
@ That sounds interesting, I am currently building a library with components for multiple front end frameworks and I thought about making them for React Native too but was worried about performance.
tldr about rn vs flutter: rn has no debug or profiling tools (but there is fancy useless ✨✨flipper✨✨ which actually takes 90% of your time when trying to read objC errors in xcode) flutter has nice tools. from this side of view there is no matter which one is faster when you can't fix your performance issues
Sir, can you suggest a way to make notes from your video in udemy. Actually it takes a lot of time to make notes, I think most of the time I am writing down everything you teach in video. So, can you make a video and guide me over that how to remember for long what I have learned.
My notes typically follow a Q/A style. This makes is easy to search if I ever forget and it helps in learning because I can test myself by answering the question. Example: Topic useStateHook > What is the useStateHook? > Code example of using the useStateHook > Anything else you want to add or make a note of related to useStateHook
I tend to write definitions and then elaborate on that element in bullet points, but will use full sentences and code examples if needed. I highlight things I'm defining or important concepts, so I can find them easily when I scan the page, and I also have an index page on each section of notes that has the number of the page and what topics are covered on that page. I retain information much better when I write it down, so this method works for me. It can be a little tedious, but it's effective, and I enjoy learning, so it's not bad. Also, if it's something that I know I'll need to get more clarification on in the future, I'll write down the module number and video number, and sometimes timestamp, so I can easily find the video.
On all his Udemy courses I follow along and keep notes in OneNote. Both typed in and with screenshots of the code. In the screenshots I also usually mark up by circling important code. And non circled code is also there for context. I organize my notes in pages and sub pages by topic. For example a page and sub pages for something like routing. I also combine info from other video courses, web sites, etc into my notes. When I need to refresh myself on a particular part of react, or the whole thing, I can just read my notes from top to bottom. Way faster than rewatching a 40 hr course! I often refer to these notes first when I get stuck on syntax. If I can't find it there then I Google it. Once I get the answer I'll usually add it into the notes for future me.
Hi Max, I've taken a few of your Udemy courses and have really enjoyed your teaching style. I'm curious of your thoughts on Elixir, Phoenix, and Liveview? Elixir is a backend language that takes the approach of logic living on the server side and diff updates are sent through websockets and relies less on the client-side (ie the trend you were alluding to in this video). In your opinion, is it just worth using a server side language at that point?
i want to learn react from scratch with updated approach and practices. from where i can start. if you have any udemy course or youtube playlist love to know. only for updated content. don't wanna waste time on previous versions then come back to new and revise my concepts again.
Why, oh God why would I choose to compute something and to pay for that calculation instead of calculating this on the client's device? Ofcourse realistically it's a matter of careful balance but if I can't cache it on the server I would rather have it calculated on the client. We now have threats in browsers, webassembly ans virtual Dom. Clients are capable enough to do it.
it's basically the 2nd most popular framework right now. Lots of use still. Just stick to one framework/library you want to master. Plenty of jobs for Angular still.
React will die a slow death, because it's not able to compete with newer frameworks like Svelte+Sveltekit, Astro, SolidJS or Qwik. Those frameworks don't need to reparse a virtual dom on any tiny change on your page. They are built from React's mistakes, and succeed at that. They include SSR and many more features. React will stay the way it is right now with few innovations. This "new direction" title is misleading. React will keep retro-compatibility for older projects, so it needs to move as little as possible to not break those projects. That's why it's obvious it cannot innovate and reach the level of newer frameworks.
React will stay relevant for user interfaces where SEO is NOT so important, all this SSR and server side routing is for SEO and SMO. To make it easier for Search engine crawlers to do their job.
@@alihaydargubatov2790 At work we are using it for 3 apps, and as the devops its a nightmare, every update almost everything breaks, still in 0.X and it really shows, for the dev team and me had been a nightmare to work with, so IMHO in the die a slow death with a lot of burnout from the poor souls we have to work with it. If you want to do a "webapp" I would try first a PWA, and second if you need something "native" I would try nativescript + svelte
I think slow death is key though. We will still be using react for next 10 years, while those newer frameworks may not be around and replaced with something even better.
@@bryanlee5522 Yeah, Cobol is still being used nowadays also, so you are very right ! But the question is, as a developer, do you want to learn an old technology, or be part of the new generation and build new projects ? It's true that if you want to be working maintaining old projects, React is a great choice. But I doubt it's a clever move in such a rapid evolving scene which is the JS scene. I believe that learning a technology that is already getting old is not the best idea. I rather would tell people to learn new frameworks and _if needed_ go work on older projects, with dying frameworks, we all need a living; But learning a new framework won't stop you from being competent in React or Angular, while only learning React or Angular could stop you from being competitive for the new projects against developers who would have learned the new ways of building webapps.
Hi 👋 Maybe you have some video tutorial on how to use Cloudinary with MongDB ? For example, I have a blog, text is stored in MongoDB, and the image is stored in MongoDB as a link to Cloudinary? Thank you in advance❤!
i just started my personal project 1 months ago with react+vite. I just finished the crud stuff. But remix seems more interesting to me, should i abandon it and move to remix? 🤣
I find it funny that we call remix and nextjs a meta framework but facebook/meta calls react a library. So where is the framework layer? Or do we all agree that react is not a library but a framework?
Question for all Devs ! I really need as much help I can get thank you🙏 I want to build a website and an android app, so people can access my product from any platform and have best experience. Both should be scalable (so in future millions of people can use them). I want to implement features like payment system, payment management (records ), gps tracking , chat, file sharing, and maybe video player (don't need voice calling,video calling etc) and other features. my questions are - How can i build them(website & app) in such a way that I should be able to scale them, when time comes and managing them would be little easy. What should be the core structure, - Seperate code base for each ? - or some different method ? Which technologies should I use to build Frontend and Backend (languages, database, frameworks, libraries etc) How will you do it ,if you want to ? Teach me your ways , masters
😁 that sounds like you want to build everything and also scale to millions of users. I think you want to do too much together at the same time. You just have to start somewhere. Scaling I would not think about yet. If your app becomes popular you probably have to refactor it anyway. Now I would focus on building features that users want.
Your first step is to work out your minimum viable product. Make it as simple as possible. Learn React, start with create-react-app (for example) and just working on your MVP.
I actually can’t be bothered with “modern” front end development anymore; being in this constant limbo-state of learning new frameworks that try and solve a problem that was already solved. I’m going back 10 years and going start building exclusively with Drupal.
it's cool, but I doubt it'll be used by many startups or companies. React for better or for worse have a lot more developers for companies to choose from. Vue unfortunately pulled a Angular v1.6.x to Angular 2 transition where a lot of libraries have yet to fully convert to Vue 3. Vue 3 itself is actually pretty nice, it's just the eco-system is having some transitional growing pains. Svelte basically needs to have one big tech and startup unicorn for it to gain traction. I haven't touched Angular in ages, but it seems that a lot of things have improved looking at the documentation. It still has a learning curve, but once mastered, you can really focus more on the architecture and design of your app as it's a full framework.
@@cknsalad770 The angular team is focusing on reducing that learning curve this year, for example using signals as part of the framework instead of relying on rxjs, also focusing on the rendering story to maybe be more like qwik or something similar.
SolidJS also has the concept of signals. One of the major selling points for it is that it's not to dissimilar to React syntax-wise. So React developers have a low entry bar to the framework. It's future is yet to be decided in terms of mainstream adoption. Svelte is great. I feel one of the things it has over the other frameworks is when it comes to building very reach UIs with animations etc. Vercel has certainly taken interest in it.
@@OsaetinEvbuoma Yeah, Svelte is great from what I have seen, but like you said it just needs that mainstream adoption. SolidJS is pretty similar to React for the most part, but I don't know if SolidJS does enough to differentiate itself to be 'X' times better than React unfortunately to the dev community and especially companies. SolidJS is still somewhat early its development stage and needs a bit more maturing. I'm kinda sad with the state of Vue as Vue 3 is great but there just seems to be a huge divide of Vue 2 and Vue 3 usage on production.
Max I have a request. In Germany they provide job seeker’s visa for professionals. There is no good video or article about explaining more details about German dev jobs. Demand for MERN stack in Germany. Which websites to find jobs inside the Germany How to find low competitive jobs Living cost , language salary in Germany Can you make a video about this. It will be really helpful for thousands of people
Great video, thanks, but... The current state of React - to add more and more means, that look like inventing a kind of a new framework each couple of months and cause a spike of articles like "How to write IDIOMATIC React this week". Sick of that...
Most of my projects need very complex data operations in the server side. That's why I always prefer writing my backend in python. In python we already have Django for server side rendering. But it is a common trend to use Django REST framework in the backend and React in frontend. With stuffs like NextJS becoming popular, non-Javascript backends will be difficult.
Not a good idea to think of NextJS as "backend" in traditional sense of backend. It's still good idea that you keep your rest api separated. Think of it as server-rendered frontend and keep it on separate service isolated from your main backend.
Bruh it's because some of the ootubers don't really implement big projects. They just build easy stuff and spread pros of it but when it comes to building and maintaining large projects it's going to become pain in the azz , it's always better to separate frontend and backend, or just do server side rendering using python frameworks or c# .net, elixir/phoenix etc
@@fdg-rt2rk Agreed. But they play a significant role role in making technologies popular. Real developers like us hardly find time to create such content.
Just a question here. Why are we using tools that, in all likelihood, are sending our data directly to the people who profit off of it? By using these frameworks aren't we just handing our clients data directly to Meta, Google, etc?
Soon to come in NodeJS/Golang : "new trend to offload the server by moving some code over to the frontend; the backend is doing too much, server costs have gone up, something had to be done"
Dude seriously, like frontend wasn't already complicated enough and they're adding backend stuff to frontend making it more complicated and heavy
Doesn't really sound good to me to do SSR. A thousand devices can handle the processing, or the server can do that fir a thousand devices, so yeah. Your server and cloud computing costs will go up.
Your remix course from Udemy is brilliant. Having taken almost all remix tutorials available, I can safely say the approach you have taken in the deepdive section to drill down the concepts is one of the best! Look forward to more Remix content from you
i used to hate react and always choose vue / svelte over it, this guy is the reason i switch to remix because of his explanation and remix got what i need (still hated react rules though, but remix offer more goods than bads for me), glad I met Maximillian and his Remix course on Udemy
:D :D :D
Year n: Just make everything simple, render everything on server and give it to them
Year n+3: Okay, the users need more interactivity, move things over to the client
Year n+6: We are duplicating a lot of code, let's move everything to the client, go serverless and just use it as an API
Year n+9: Okay, the client side things are getting heavy move some things back to the server
> Repeat...
iNoVaTiOn
Love your videos, Max. Random but whilst I'm here, your React and React Native courses literally changed my life. Now working full-time as a developer. Your Udemy courses made this possible. Thank you 🙌
I could literally make the same comment. Lol
stop the cap
This inspired me to rewatch your NextJS course. I never finished it because I didn't like the idea to mix backend and frontend in the same project, but now it makes more sense. Plus I don't have to use two different technologies like React for fronend and NestJs/ExpressJS/PHP for the backend.
@avfr What exactly do you mean? What wouldn't be possible in a Nextjs API route (endpoint)?
@@avfr3987 I think any API endpoint + DB communication can be implemented in NextJS
@avfr is NextJS bad for fullstack? Sorry I'm new at it and still learning
React js is a blasphemy for JavaScript community. React nonsense must be banned across world plane. This f library makes web development unnecessarily complicated.
Angular is far better than svelte and react nonsense., because it leverages rxjs subscription, angular service make communication between sibling components much easier, developers know what exactly is happening.
Svelte and react have confusing code. Developer experience matters.
@avfr Ohhhh I see I see. Yeah it really depends what you need, but if that's the limitation it might cause you issues in the long run since you don't necessarily know at the moment that you might need those features in the future.
Great summary, interesting even for non React developer! Could we expect similar videos for different frameworks? I think it would be amazing to hear your thoughts about current state of Vue or Svelte!
Current state of Vue: awesome. Major players in ecosystem finally updated to Vue 3 (Nuxt 3, Vuetify). Evan and the Vue team will be improving Vue 3 1st half of 2023, then work on Vue Vapor (Vue using SolidJS tech for even smaller size and faster performance) in the 2nd half 2023. So, Vue is not bleeding edge tech like Solid JS, but it is far far more mature than Solid and Svelte as well. React is very heavy in comparison, much more complicated, though Next/Remix/et al. are working to simplify. I think 2023 is going to be a marked incline in Vue usage as Vue 2 gets phased out and folks start seeing how all-around great Vue 3 is. I'm looking into Astro with Vue for one of my projects, as Astro 2.0 just came out, meaning it's pretty decently mature, and I think Astro plays better with game engines/frameworks since it stays closer to HTML than Vue, which is off in SPA/JS-la-la-land ;).
I'm on my way on completing your React The Complete Guide Course, and so far, I really love it! Thanks Max!
It would be great to see update of PWA course. There isn't much up-to-date materials to get familiar with this topic so it would be great if you provide it.
I like that Dev eloper image you have 😂
+ I'm also😂👍
@@jamesmay5088
And I also like your name James May from Top gear 😂
@@mohamedatef2383 It's a fake name. Are you a fan of Top Gear? I've watched all seasons of old version of Top Gear, and of course The Grand Tour. I'm also looking for 2 season of Clarson's Farm. And you?
u can watch developer with 72 others.
😂😂😂
Max your udemy courses have saved my life... It's life-giving Thank you for being a teacher to me and millions of students
There are people saying that the significance of the changes between between Next 12 and 13 make Next 12 courses obsolete at this point. What do you guys think? I just finished a React course and had planned to start learning Next soon. Should I study Next 13 even though it's still experimental? Or should I study something else on my list while I wait to see how things play out with Next 13?
Did you really bring angular and vue to compare and forgot svelte?
Soon we will be back to PHP server side websites because all that time that we did frontend apps PHP used to better its serverside frameworks.
hello,Mr max.thanks for your course.i've learned js almostly one and half years.but I'm still in a primary level.and your course help me understand some basic concept knowledge.you're always sophisticated and skilled.your idea also inspired me.i really appreciated your guidance.And i hope you make a course of Vue 3 . thanks a lot Mr Max.
React is my daily driver for my employers. Sometimes the occasional vue app. But whenever I get a chance, I roll svelte 💪
"There are two types of frameworks. Ones people love, and ones people use."
MAAAAX! Good to find your videos again. :)
We came from PHP to front end frameworks… and back to PHP 😂
Hi Max, will you update your Next.js course on Udemy to cover v 13?
Thanks, this really summed it all up nicely. It's funny that we're going full-circle in web development, back to the server. When I started, we built business apps in PHP, ASP, .NET, Java, etc. that were server-side monoliths, performed quite well for a decent user load, and were many times easier to build/maintain than a modern microservices arch w/ a React front-end, for example. You could actually be an *expert*, in-depth full-stack developer and reasonably keep up with changes and updates. Let's be real - we're not all Facebook and Amazon...most of us are seriously over-engineering solutions. It was a simpler time...ahhh...Pepperidge Farms remembers!
I am sorry but I have to disagree on this. Before even with PHP you still had to write your frontend in JS and unless it was a really basic app, with barely any interaction, you had to add something such as jQuery (or manipulate the DOM directly). Further I always found PHP far tor verbose as a language, although of course this is a personal opinion. Now though, with something like NextJs I can write a full app which fetched and render data, sneak in some animations as well, some nice styling, and good performances in just a couple of days, while before it would have took me at least a couple of week. Further I can deploy my app, for free, with no configuration needed in something like Netlify or Vercel.
So while I agree that JS is kind of going back to some of the PHP principles, I also believe it is doing so in a much simpler and more efficient way.
@@_scrapbookers_ Not true. I was writing highly-interactive web apps between 1998 and 2012, that used hardly any JS on the front-end. Just because you're rendering on the server doesn't mean the app isn't "highly interactive", it just means that pages refresh more often. Nothing about the current state of full-stack development is simpler than it was, in those days, in my opinion. I'm not a fan of PHP, personally, and would have chosen any of the other technologies I mentioned, over them. Was just an example of the concept, wasn't opining on the language itself.
@@VincentJenks Yes of course you could do that, but refreshing pages every so often is not the best user experience IMO, particularly when users are connected to slow networks, as the website feel very slow.
I agree that often people tend to over engineer solution, but I also believe that today, with framework such as React & Next, coupled with something like Tailwind, you can write a beautiful looking, responsive, highly interactive and SEO optimised app, in under a couple of days. I guess it always comes down to what technology someone is most familiar with. I would certainly feel much more confident, and therefore develop much faster using a JS/TS stack, rather than relying on PHP.
@@_scrapbookers_ I understand all that, and that's how I build apps today - you're preaching to the choir a bit. Never was I advocating for an old school server-side approach or recommending PHP. My original point was - the frontend has become a pig and there are frameworks on top of frameworks, and just too much engineering happening, across the stack. The front-end having server-side access is a good thing and may help.
If we are going back to the server, thus PHP will become more relevant than that already is.
Great the most popular framework is the one that doesn't have stable features. Not surprising that so many React apps are unstable.
New features are going to be unstable initially. No way in hell you are a developer, if you don't know this much.
@@vikrantsingh47 The problem is that even old features are unstable
@@IStMl like?
We need more metrics on successful projects built with react, angular, vue etc.
Please update the Nodejs course. Love from India
Isn't moving more code on the server old fashioned?
what about React Native is it trending similarly to move code server side?
excellent summary.
The only thing is that even though Hooks is a standard, most of the examples are still created using classes. I don't know why people keep doing it, although maybe I'm just lucky with the search results))
It probably is just legacy examples that still need to be updated, since hooks are a newer thing and many examples were written some time ago
I see with my little eye, a legendary art with some white text, and black text with a yellow background
Please make a video on State of angular!
I absolutely love NextJS 💚
One question I rarely see addressed in these discussions of moving computation back to the server - isn't that expensive? If your app scales to a million users, or even more, and most of the work is done client side, there's no/little extra cost to host it.
But now using a framework like remix, even with caching, there's going to be more and more computation on the server as you get more users and that costs more. As you mention in the video that's not a problem for big companies like Facebook but the whole point of these improvements is to make this easier for small teams, right? A surprise $100k AWS fee because your app went viral, or getting cut off by Vercel at exactly the point where you're getting popular is a problem. Doing most of the work client side prevents this problem.
Until I see this issue clearly and directly addressed I'm going to stick with the old way. I've chosen not to use Remix for this reason.
I was just thinking the same thing
Very wise.
Can u do a state of Anglular video?
I'm currently looking for my next role as a senior developer and, what I'm noticing, particularly here in the UK anyway, is that a lot of jobs seem to be going Angular! Anyway, I'm far too old to play the "tech flavour of the month!" game! I'm already heavily invested in React, and I'm already thinly stretched as a full stack dev trying to keep up with an increasingly relentless backend too! One cannot learn it all! So it's React or bust for me! At least on the frontend anyway!
Really love your courses. Will you start using TS eventually?
Developer 👍👍👍
Loved that video! Keep it up man💪🏼
Thanks, Max! I have been working in angular for two years and exactly was wondering "how react is doing" these years! Super actual!
thank you mr max i'm new to React and learning it right now on udemy hopefully to become real react developer.
i don't use reactjs anymore. i use Nextjs, typescript, tailwindcss, zustand + react-query, trpc or prisma, auth0 and stripe + cloudinary.
these stacks is really good for ReactJs developers. almost anything you can build with front-end heavy applicatons.
That's a very reasonable and good-DevEx stack right there.
Next uses React though
That’s literally react with extra steps
No way
Hmm, Next.js is a react framework so, that is not true
More logic on the client side = less secure! Application logic should be as much as possible on the server side like it always has been.
i dont understand how can we avoid the useEffect hooks with SSR.
I am not sure if I should learn redux because it looks like Nextjs does not use it much. Any advice?
Those posters in the background are great where did you get them from?
this is making me hooked in using react more as a library
SPA first frameworks were a huge error. After that error everyone is now migrating to SSR frameworks like Nextjs or Remix. We should have started with SSR first and gradually migrate to more and more SPA when possible.
Please make similar video about current state of VUE :)
Angular wins with its reliability and extensive documentations.
They are all trying to do now what php has been doing all along !!!
Wtf
Is thal all because you love php
Haha i see
@@mohabedr5030 can you list how his statement is incorrect?
React js is a blasphemy for JavaScript community. React nonsense must be banned across world plane. This f library makes web development unnecessarily complicated.
Angular is far better than svelte and react nonsense., because it leverages rxjs subscription, angular service make communication between sibling components much easier, developers know what exactly is happening.
Svelte and react have confusing code. Developer experience matters.
@@Almighty_Flat_Earth If experience matters why is Angular low in DX rankings?
That's a great overview. Kudos ✨
Do you teach this in any course you offer?
Firstly, they invented a complicated reactJS library that included too sophisticated Redux and children components which should be protected by 'useMemo' and 'useCallback' hooks in order to avoid unnecessary re-renders and what we see now: they suggest more experiments?! Why? To make our development easier?! Honestly, I do not understand why you love this library...
Vue is much more elegant
react SPA will stay the same, but Next/Remix will have some huge updates this year!!!
and I hope React Native new architecture will be more mature!
React Native new Architecture? What is this about? I wanted to do a mobile app but because JS bridge I started looking into Flutter.
@@DanielNistrean RN new arch is the replacement for JS bridge, hence improve overall performance
@ That sounds interesting, I am currently building a library with components for multiple front end frameworks and I thought about making them for React Native too but was worried about performance.
tldr about rn vs flutter: rn has no debug or profiling tools (but there is fancy useless ✨✨flipper✨✨ which actually takes 90% of your time when trying to read objC errors in xcode)
flutter has nice tools. from this side of view there is no matter which one is faster when you can't fix your performance issues
i think i need to relearn it from basics now!
4:01 the vue pick is so curious
What's up with the Vue spike? 0:06
I downloaded in a couple of times
I like your clarification on the distinction between a framework and a meta framework. 👍
Please make a node and express.js tutorial
Sir, can you suggest a way to make notes from your video in udemy. Actually it takes a lot of time to make notes, I think most of the time I am writing down everything you teach in video. So, can you make a video and guide me over that how to remember for long what I have learned.
My notes typically follow a Q/A style. This makes is easy to search if I ever forget and it helps in learning because I can test myself by answering the question.
Example:
Topic useStateHook
> What is the useStateHook?
> Code example of using the useStateHook
> Anything else you want to add or make a note of related to useStateHook
In case of re-reading your notes, just rewatch the vid.
My trick is using comments in VS Code.
I tend to write definitions and then elaborate on that element in bullet points, but will use full sentences and code examples if needed. I highlight things I'm defining or important concepts, so I can find them easily when I scan the page, and I also have an index page on each section of notes that has the number of the page and what topics are covered on that page. I retain information much better when I write it down, so this method works for me. It can be a little tedious, but it's effective, and I enjoy learning, so it's not bad. Also, if it's something that I know I'll need to get more clarification on in the future, I'll write down the module number and video number, and sometimes timestamp, so I can easily find the video.
On all his Udemy courses I follow along and keep notes in OneNote. Both typed in and with screenshots of the code. In the screenshots I also usually mark up by circling important code. And non circled code is also there for context. I organize my notes in pages and sub pages by topic. For example a page and sub pages for something like routing.
I also combine info from other video courses, web sites, etc into my notes.
When I need to refresh myself on a particular part of react, or the whole thing, I can just read my notes from top to bottom. Way faster than rewatching a 40 hr course!
I often refer to these notes first when I get stuck on syntax. If I can't find it there then I Google it. Once I get the answer I'll usually add it into the notes for future me.
im surprised you didnt mention svelte and sveltekit!
Really love your courses. Will we have any updates to the NextJS course on Udemy?
Please do a new video of Angular taking a new direction too.
Hey, you look familiar. I think I used one of your React course when I started react, the one with the hamburger app 😂
Hi Max, I've taken a few of your Udemy courses and have really enjoyed your teaching style. I'm curious of your thoughts on Elixir, Phoenix, and Liveview? Elixir is a backend language that takes the approach of logic living on the server side and diff updates are sent through websockets and relies less on the client-side (ie the trend you were alluding to in this video). In your opinion, is it just worth using a server side language at that point?
You either curious what his thought are, or you need to explain it to him. Not both lol.
Awesome overview Max 👌😊
i want to learn react from scratch with updated approach and practices. from where i can start. if you have any udemy course or youtube playlist love to know.
only for updated content. don't wanna waste time on previous versions then come back to new and revise my concepts again.
Why, oh God why would I choose to compute something and to pay for that calculation instead of calculating this on the client's device? Ofcourse realistically it's a matter of careful balance but if I can't cache it on the server I would rather have it calculated on the client. We now have threats in browsers, webassembly ans virtual Dom. Clients are capable enough to do it.
Suspenses, hooks or composables... Max are we talking React of Vue3 I am confused
Angular has future right ?
4:00 I wonder why Vue had a 1000% spike in downloads for a month or two? Bit strange
Svelte had the same, seems like somebody found a way to "hack it", and then a week later someone did the same for Vue
@CAS Vue is amazing, especially coupled with Nuxt 3
You remix class is great. Thanks.
I did contribute to the spike, but only because of my job. I'd much rather use Svelte.
I would be nice to see a video on AnalogJS from you guys.
I like new React stuff, but after SvelteKit I can’t go back. At least for personal projects, since companies only knows react.
What about Angular?
it's basically the 2nd most popular framework right now. Lots of use still. Just stick to one framework/library you want to master. Plenty of jobs for Angular still.
Max you should publish a course on building a complex enough application
React will die a slow death, because it's not able to compete with newer frameworks like Svelte+Sveltekit, Astro, SolidJS or Qwik. Those frameworks don't need to reparse a virtual dom on any tiny change on your page. They are built from React's mistakes, and succeed at that. They include SSR and many more features.
React will stay the way it is right now with few innovations. This "new direction" title is misleading. React will keep retro-compatibility for older projects, so it needs to move as little as possible to not break those projects. That's why it's obvious it cannot innovate and reach the level of newer frameworks.
React will stay relevant for user interfaces where SEO is NOT so important, all this SSR and server side routing is for SEO and SMO. To make it easier for Search engine crawlers to do their job.
What about react native?
@@alihaydargubatov2790 At work we are using it for 3 apps, and as the devops its a nightmare, every update almost everything breaks, still in 0.X and it really shows, for the dev team and me had been a nightmare to work with, so IMHO in the die a slow death with a lot of burnout from the poor souls we have to work with it. If you want to do a "webapp" I would try first a PWA, and second if you need something "native" I would try nativescript + svelte
I think slow death is key though. We will still be using react for next 10 years, while those newer frameworks may not be around and replaced with something even better.
@@bryanlee5522 Yeah, Cobol is still being used nowadays also, so you are very right ! But the question is, as a developer, do you want to learn an old technology, or be part of the new generation and build new projects ?
It's true that if you want to be working maintaining old projects, React is a great choice. But I doubt it's a clever move in such a rapid evolving scene which is the JS scene.
I believe that learning a technology that is already getting old is not the best idea. I rather would tell people to learn new frameworks and _if needed_ go work on older projects, with dying frameworks, we all need a living; But learning a new framework won't stop you from being competent in React or Angular, while only learning React or Angular could stop you from being competitive for the new projects against developers who would have learned the new ways of building webapps.
Wow that's so cool!
*chooses SolidJS*
Hi 👋 Maybe you have some video tutorial on how to use Cloudinary with MongDB ?
For example, I have a blog, text is stored in MongoDB, and the image is stored in MongoDB
as a link to Cloudinary?
Thank you in advance❤!
i just started my personal project 1 months ago with react+vite. I just finished the crud stuff. But remix seems more interesting to me, should i abandon it and move to remix?
🤣
I find it funny that we call remix and nextjs a meta framework but facebook/meta calls react a library. So where is the framework layer? Or do we all agree that react is not a library but a framework?
So we've circled back to PHP and jquery
Let's herd again, and do keep circling every 10 years
Question for all Devs !
I really need as much help I can get thank you🙏
I want to build a website and an android app, so people can access my product from any platform and have best experience. Both should be scalable (so in future millions of people can use them). I want to implement features like payment system, payment management (records ), gps tracking , chat, file sharing, and maybe video player (don't need voice calling,video calling etc) and other features.
my questions are -
How can i build them(website & app) in such a way that I should be able to scale them, when time comes and managing them would be little easy.
What should be the core structure,
- Seperate code base for each ?
- or some different method ?
Which technologies should I use to build Frontend and Backend (languages, database, frameworks, libraries etc)
How will you do it ,if you want to ?
Teach me your ways , masters
😁 that sounds like you want to build everything and also scale to millions of users. I think you want to do too much together at the same time. You just have to start somewhere. Scaling I would not think about yet. If your app becomes popular you probably have to refactor it anyway. Now I would focus on building features that users want.
Your first step is to work out your minimum viable product. Make it as simple as possible. Learn React, start with create-react-app (for example) and just working on your MVP.
Thank you very much for this great information....
still I find svelte far better now than react and even more fun with version 1.0 sveltekit you can make fullstack application
same but I cant find a job with svelte, I have to use React
I actually can’t be bothered with “modern” front end development anymore; being in this constant limbo-state of learning new frameworks that try and solve a problem that was already solved. I’m going back 10 years and going start building exclusively with Drupal.
I can tell that you are unemployed.
😀 just dey play
To willingly use drupal means you must be some type of masochist.
Inspiring to go back to our roots
Angular is growing by the way now
Most hated framework in stackoverflow survey
What are your thoughts on the state of frameworks like SolidJS in 2023?
it's cool, but I doubt it'll be used by many startups or companies. React for better or for worse have a lot more developers for companies to choose from. Vue unfortunately pulled a Angular v1.6.x to Angular 2 transition where a lot of libraries have yet to fully convert to Vue 3. Vue 3 itself is actually pretty nice, it's just the eco-system is having some transitional growing pains. Svelte basically needs to have one big tech and startup unicorn for it to gain traction. I haven't touched Angular in ages, but it seems that a lot of things have improved looking at the documentation. It still has a learning curve, but once mastered, you can really focus more on the architecture and design of your app as it's a full framework.
@@cknsalad770 The angular team is focusing on reducing that learning curve this year, for example using signals as part of the framework instead of relying on rxjs, also focusing on the rendering story to maybe be more like qwik or something similar.
SolidJS also has the concept of signals. One of the major selling points for it is that it's not to dissimilar to React syntax-wise. So React developers have a low entry bar to the framework. It's future is yet to be decided in terms of mainstream adoption.
Svelte is great. I feel one of the things it has over the other frameworks is when it comes to building very reach UIs with animations etc. Vercel has certainly taken interest in it.
@@OsaetinEvbuoma Yeah, Svelte is great from what I have seen, but like you said it just needs that mainstream adoption.
SolidJS is pretty similar to React for the most part, but I don't know if SolidJS does enough to differentiate itself to be 'X' times better than React unfortunately to the dev community and especially companies. SolidJS is still somewhat early its development stage and needs a bit more maturing. I'm kinda sad with the state of Vue as Vue 3 is great but there just seems to be a huge divide of Vue 2 and Vue 3 usage on production.
@@cknsalad770 SvelteKit is backed by Vercel now. I think it’s going to be great!
when did Seth godin started teaching react.js?
Thank you!
Hello ! Please do a video series tutorial on Analog !
Thanks Max for another interesting video
But why the trend is shifting to server side again !?
Max I have a request. In Germany they provide job seeker’s visa for professionals. There is no good video or article about explaining more details about German dev jobs.
Demand for MERN stack in Germany.
Which websites to find jobs inside the Germany
How to find low competitive jobs
Living cost , language salary in Germany
Can you make a video about this. It will be really helpful for thousands of people
React it's like a disco song, Angular pop one, it will be there for years
I think the thing with server components is an over-engineering
Great video, thanks, but... The current state of React - to add more and more means, that look like inventing a kind of a new framework each couple of months and cause a spike of articles like "How to write IDIOMATIC React this week". Sick of that...
You didn't talk about devEx which is a huge aspect of the work
Most of my projects need very complex data operations in the server side. That's why I always prefer writing my backend in python. In python we already have Django for server side rendering. But it is a common trend to use Django REST framework in the backend and React in frontend. With stuffs like NextJS becoming popular, non-Javascript backends will be difficult.
Not a good idea to think of NextJS as "backend" in traditional sense of backend. It's still good idea that you keep your rest api separated. Think of it as server-rendered frontend and keep it on separate service isolated from your main backend.
I need to explore NextJS myself... I don't have much idea... Thanks for your suggestions...
Bruh it's because some of the ootubers don't really implement big projects. They just build easy stuff and spread pros of it but when it comes to building and maintaining large projects it's going to become pain in the azz , it's always better to separate frontend and backend, or just do server side rendering using python frameworks or c# .net, elixir/phoenix etc
@@fdg-rt2rk Agreed. But they play a significant role role in making technologies popular. Real developers like us hardly find time to create such content.
React is the Windows/Goliath of frameworks. I'm goin with Solid
Just a question here. Why are we using tools that, in all likelihood, are sending our data directly to the people who profit off of it? By using these frameworks aren't we just handing our clients data directly to Meta, Google, etc?