Too good NOT to share.
My brothers and sisters in Christ I want you to know that I care about your souls enough to share these truths with you:
- You don’t need JavaScript to make a web page.
- You don’t need JavaScript to write styles.
- You don’t need JavaScript to make an animation.
- You don’t need JavaScript just to show content.
No we don’t need it. But is it better if we use it? Like, you don’t need OOP for implementing literally anything either.
When you hold a hammer everything looks like a nail. Just because it’s useful in some cases doesn’t mean it’s always the best solution.
The article mostly rants about front end devs using unnecessarily complex solutions for simple problems. Like using React for generating static web sites.
I get what he means and in most points I agree (I’ve worked primarily as a front end dev so far in my career), but as you get more familiar with these frameworks they tend to be so much faster to iterate on compared to a more “cleaner” setup. I’ve seen plenty of situations where using such frameworks were clearly overkill, but were still much faster to setup and were ready to be expanded on if needed in the future. Everything about the package ecosystem on web dev he’s 100% on point though. Things like the left pad situation are insane.
I feel like this is more like a hammer vs bare hand situation. If the point is there is a place and time for everything (except VBA) then I agree.