I love that this video is a high-level, non-detailed overview and covers the evolution of frontend development. I think even my management can understand it. I'm going to suggest they watch it so they have some idea how the sausage is made.
Nice video but I suspect that if you didn't spend the last few years fighting with all this 💩 you won't understand much and/or come out with a headache... I'll show it to my nephews studying webdev, we'll see how they react 😂
No SPA stuff for me, I've been working for the same company for nearly 20yrs now developing the web based point of sale that all our stores use. All MVC on the backend but still an MPA. Exceedingly fast system especially processing the HTML pages ready for display to the user. Time to first paint and time to first byte are both very very quick. Nobody needs modern JS frameworks, people just choose to use them because they like to make things difficult for themselves :P About the only thing I've been doing for the last 14yrs is this fad word called 'hydration', but I was doing it long before it was even a known word for this kind of thing :P I send the processed HTML page, then I have javascript which makes a backend request to get the rest of the data, I then have Template7 make it visible on the page. Used to use Mustache and Handlebars but found them rather limiting.
How much traffic are you getting on your system? Is it still fast on concurrent users? Is the team you're working on large enough to even consider Dev Experience? How is the maintainability of your app? How quick are you shipping new features or fixing bugs?
11:31 wait… hydration?? That’s not right. SSR usually sends down the data as HTML. Aka the HTML is rendered on the backend not on the front end. JS might be added to add some local interactivity… but hydration is basically mixing CSR techniques with SSR techniques.
learning this high level architecture, boosted my confidence in learning , i am thinking ill build projects after projects to learn the things rather than going through books only.
I have started learning web dev and currently learning networking section. please how much deep should i go while leaning? for example : i am building http server to get internal working hands on. but then it will take eternity for me if i follow this model to learn everything how much should i learn., or should i just start building applications in huge numbers, this will brush my industry standards used things
I would add that react has one directional dataflow (I guess they call it one way binding) which suits well for functional approach, since components are functions calling functions.
The biggest lie in web development is the last 9 minutes of this video. You don't need SPAs and frameworks for good UX. Traditional MPA, with some htmx and JS sprinkled where necessary, will give close enough the same (or better) experience, but with much less effort and complexity.
But this is how the video is ending - SPA has flaws and the best solution is MPA or a hybrid approach. And this is not my take, this is what the community shifted to in recent years.
I am glad that I didn't click the video based on the title. I clicked it as I saw the thumbnail and thought that its a collective information of experience and got that exactly😊.
Waste of time. I thought i already banned this channel from recommendations. Jesus youtube, why cant you be simple just like the guy in the video told you
@@awesome-coding don't be mad at me. I'm mad at youtube because it keeps bringing your videos. Not at you. Someone loves your content, doesn't mean you should stop because of some salty dude (me) on the internet
Would be nice to have one focusing on the backend... even thought MVC has been here for ages we also had new additions with GraphQL, Event Systems, No-SQL, horizontal scaling and more
A little beside the point but, given that laravel has been getting a lot of attention lately do you have any plans on trying it? It was one of the first frameworks i tried with barely any experience in web dev and i most admit i was surprised with how much i could with so little time with not much prior knowledge in web dev and laravel.
For those who may wonder what’s so good about php: Immutability by default (copy-on-write); Stateless by default (whole script is whipped out when it’s done , state can be kept between requests just through sessions and persistent storage); Predictable scaling (stateless makes easy to reason about performance); Full OOP support (classic Java-like OOP with interfaces, private fields, final and readonly stuff); Easy to deploy (no need to rely on aws and other pass, just get vps and play with nginx and fpm); Rich stdlib esp for web (node.js requires 3rd party code for basic stuff); Great performance since PHP 7 for interpreted single threaded language (opcache, preload, jit if needed);
Thanks for sharing your experience and real world journey in tech,DRY and KISS is still the best practice. I'm in love with SPAs Angular is still given me a better developer experience on large scale project❤
For any beginner and every developer who is huble enough to lern, this is the right Video!. For context: I'm a senior developer of the webarts myself. So i can tell he knows what he's talking about. I love how holistic and simple you explained it! ❤
I have started learning web dev and currently learning networking section. please how much deep should i go while leaning? for example : i am building http server to get internal working hands on. but then it will take eternity for me if i follow this model to learn everything how much should i learn., or should i just start building applications in huge numbers, this will brush my industry standards used things
This is a great overview of the “what” of web dev. The devil (or the fun part, IMHO) lives in the details of the “how” and especially the “why”. I think one thing that helps define a more “senior” level of expertise in the field is diving deeper into (and debating) the theory of _why_ things are built the way they are; speculating on how we can improve it. Much of that is informed on a deep understanding of the history of how we got here (thanks for that) as well as years of experience dealing with issues that need to be overcome by new standards, libraries or ways of thinking.
@@patricknelson check out the keynote talk by DHH, creator of Ruby on Rails, just out today. He blasts the current complexity of things. It’s a great talk actually.
It makes us look experienced and cool. You really need to know your stuff in order to cut through the bullshit and do your job right. So I might charge you $200 / hour to implement a basic form with some actions, but you'll know that those 40 billable hours are well deserved ✌️
As a user I prefer SPA. In 2024 we have really good internet, so initial load doesn’t take long, and it feels a lot better to use. As a developer I also prefer SPA as it’s a better dev experience.
In what way do you prefer SPAs as an user? If you are talking about navigation (Client-side routing), you can have it with Server-side rendering. Most meta-frameworks work like that by default. SvelteKit for example, as long as it can load the javascript, will work as a normal SPA, with client-side routing and fetching in the browser when new data is needed. If it can't load the javascript part, it will default to MPA mode, where every action triggers a full refresh.
Think about your clickbait title. You might gain views on this particular video, but you will lose the people who are genuinely interested in watching your videos.
Why is this click bait? The agreed idea in the industry is that web dev is complex because of all the frameworks and tools you need to know. Would you agree? My argument is that all this complexity is smoke and mirrors, and that things are actually easy. You have a handful of concepts and ideas you need to understand and you should be good to go. Things are actually so simple that you could do a full overview of the space in 10 minutes. So the lie is the aparent "crazy" state of the web dev in general. Would you agree with this? If not, I will actually consider changing the title :)
The agreed idea in the industry is that web dev is complex because of all the frameworks and tools you need to know. Would you agree? My argument is that all this complexity is smoke and mirrors, and that things are actually easy. You have a handful of concepts and ideas you need to understand and you should be good to go. Things are actually so simple that you could do a full overview of the space in 10 minutes. So the lie is the aparent "crazy" state of the web dev in general. Would you agree with this?
@@awesome-coding Isn't the web complexity (mostly frontend) ever changing frameworks and tools and dependencies which can and will break each other over time? The concept may not be hard until you start using the modern frameworks and 1) something doesn't work because you are not doing todo app and need complex feature, but the framework haven't though about it and in addition hide the implementation 2) your framework updates and then you are on legacy stuff along with bugs or you try to move on, but first you have to update to the new "correct" mental model? You should'nt have to start with framework on top of your framework to do a todo app which maybe is calculating in parallel alternative DOM, because why not. And then you have backend. Spring boot with java, dotnet core with c# their development and slow and steady, they focus on not breaking changes and even if they do, the are doing version bump (no, not every 6 months like next) and very good documentated way to migrate to the new version, often with over 90% backward compatibility.
