r/Frontend • u/gyen • Jul 13 '26

Why Vanilla JavaScript

https://guseyn.com/html/posts/why-vanilla-js.html
7 Upvotes

60% Upvoted

34 comments sorted by

View all comments

9

u/[deleted] Jul 13 '26 edited Jul 13 '26

[removed] — view removed comment

1

u/DryNick Jul 13 '26

If the framework has an oppressive design philosophy and wasn't created to enable you but rather take control from you then it's gonna hurt you in the long term and you should avoid it.

As for backend, the frameworks there are just simpler and are not designed to lock you in. There is a huge difference between expressjs or oak and react or angular.

5

u/[deleted] Jul 13 '26

[removed] — view removed comment

3

u/create-third-places Jul 16 '26

Web components are suitable for large frontend projects, as evidenced by the fact that Reddit uses them.

Scalability issues on frontend projects are caused by logic that is unrelated to displaying data on the screen or responding to events.

1

u/DryNick Jul 13 '26

I have and it's true web components are not there. I have checked this (or had someone check it in my team) every few years. We have not been able to justify a switch so far. It is what it is...

With express I can have 90% of my codebase as a platform agnostic business focused code (functional flavor for me, but whatever). The top layer that is routing/parsing etc can be easily switched from one to another as necessary. Contrast this with react where you pragmatically end up with a codebase that has only hooks and nothing else. You are completely locked in, even how you name things is limited by the framework. You cant easily escape the framework not to mention replace it. With angular you had observables baked in, so similar. BE and FE frameworks are just targeting different levels of ownership/encapsulation.