[anotheracctfo]

I'm amazed at how many developers need ridiculous complexity to feel like they've accomplished something. I feel that too many people are focused on building resume keywords than solving problems.

If you can solve it in 20 lines of CSS / JS then do it.

[oxff]

You don't get hired for, say, a role that requires Svelte / React expertise by pointing out "I did it in vanilla JS!" - so you are correct, industry sets the rules and your CV if you want a job from them, needs to reflect this.

There are also software engineering (not programming) reasons, mostly because they set standards for stuff like state management, for why they're useful - helps with future maintenance, documentation etc. when you don't have to interpret a custom self-made framework and teach it to hires.

[dieselgate]

Yep my thoughts as well. It’s great to use vanilla js for a personal website (I do) but if one is seeking employment knowing a popular framework (both backend and front end) is also critical.

It also seems worthwhile from an Org standpoint because then they can target “react” or “vue” developers in job postings who can presumably hit the ground running productivity wise.

(This is basically just echoing everything parent comment was saying)

[Existenceblinks]

Poll

- Job market sucks

- Industry sucks

- JS framework sucks

- Developer sucks