@fistofsage

That's the thing: frameworks were originally built for the purpose of solving issues coders had; now they're just "products" being shoved out there with hopes of become "the new profitable wave/trend"

@mbahmusalto

As a frontend developer, I approve this content

@gauravphogat394

As a frontend dev. Understanding these so callled simpler next.js, material UI and typescript code in my new job takes about 80% of my time. Just understand not chaning anything at all still.

@RamssCoreM

As a frontend developer, I can't feel more related to this video. Frontend job offers now became a cancer, asking you to either be a backend dev, a devops-aware dev, a designer, UI/UX master, having knowledge of 10 different frameworks to FUCKING RENDER STATIC HTML.

@tomcoop9750

I can do all I need with vanilla JS, php, bootstrap, and sql.

@summerWTFE

That's why I'm making a new framework that's much easier than all the others!

@wltschmrz4402

I don’t know if it’s 2025, but I think at least since I started working in it (10-11 years ago) frontend always had those shiny new frameworks each year and was mostly hype driven

@nghianguyen170192

Frontend Frameworks went through the whole life cycle with new hype names. Back in my day, html, css, vanilla JS and Jquery and I can build the whole damn SPA on that.

@crackprotein-p3p

As an ex frontend developer I really hate frontend development

@mayukhchakraborty5364

Exactly the reason why I personally went frameworkless from last few months, and it's working out great. Who know? Maybe I wil upload the frameworkless series in yt as well 😂😅

Edit: [TRIGGER WARNING] Apparently using vanillaJS is uncool? Lol who cares about coolness, just ship apps man.

@adityarajsingh8110

Back in 2019, I gave my loyalty to angular, kept updating myself to the newer versions. and I must say,..................It never dissappointed me. Though I will agree, I have experience with coding so angular was breeze for me. For anyone who hates coding, it will indeed be tough

@Cyphlix

"and how to animate a button with a compiler you didn't ask for" god, its too real

@errolisdynamic

This is why I’m a backend developer

@Michael-im5mq

I do frontend dev work and I agree. I just stick with vue because it gets the job done for me personally. Jumping from one framework to another just because it is trending on social media is nonsense but I can see why this might appeal to junior devs

@Krypteia9

Serious companies don’t give a dog’s ass about these baby frameworks in the first place. Only startups and hobbyists play with them. No serious company would invest in a framework that is less than 10 years in the market.

@programmeryk5659

i use just laravel & blade

@ajth-in

Noticed a lot of new channels talking about this exact topic lately. And yeah, modern front-end stacks are definitely complex, but so are today’s requirements. Just because new frameworks pop up doesn’t mean you need to rebuild your whole codebase every time. Honestly, isn’t it a good thing that we have options? 

Personally, I do something like this: if the site is simple and mostly static, I go with a templating engine or even HTMX. But once things get more complex and more interactive , React or Svelte really start to shine. As for the newer server-side approaches, I think they offer a great middle ground between rendering everything on the client and everything on the server. They give you control to fine-tune performance and interactivity. The key is to find the tool that fits your specific needs.

@iamcasted

When I started learning Go, Rust and CPP I instantly got derealisation (not joking, had to see a doctor). Turns out the world I live in is not changing 5 times per day, and there (god forbid) even are tools that have not been updated for years because they are complete pieces of software 🤕

@ShaferHart

The reality is that Angular was always the right choice (or something similar in approach but they're the only ones really doing it that way). One framework, all batteries included, organized in such a way where you literally can’t mess up the workflow unless you try really hard. But people still aren’t ready for that conversation. All those YEARS people have spent learning random libraries and BS concepts could’ve been spent productively if the market had just settled on Angular. But whatever. I left “full stack” (did both Angular and React) and went back to backend as soon as I could. Looks like things haven’t changed much 😂

@Puleczech

I am not even a developer but was asking this my developer colleagues two years ago already. It has always been one of the main reasons why I never got into coding because it felt like there is a high chance of spend insane amount of resources on something that will be proclaimed obsolete few years (or months? or weeks?) down the road.