"vanilla JS" - yea that is a big no-no for me these days..
I'm not a fanboy of frameworks, but I would not touch a project without some "published framework".
If you DON'T pick/use a framework.. you STILL are using a framework. Just a framework that YOU invented, that doesn't come with documentation, examples, best practises and 1000 questions on StackOverflow.
Ever worked on a JQuery project with more than 3 people or one that took longer than 6 months !? Its a nightmarish mesh !! Since there are no std ways todo stuff.
Thats what the frameworks gives you, documentation, examples, Q&A and std practises (some are even best practises).
I'm sure once you start asking around for the experts and their opinion they will tell you why the framework xyz is wrong but honestly at least everyone on the team and the poor consultants that comes after you, can be "consistently wrong" and know where to jump into this project.
Rant-over sorry :) But "VanillaJS and/Or Clean Jquery"
Yea no just no.
Php: Yea its a mess but a simple mess to get going :) As per first comment.
I keep hearing this "no framework == homegrown framework" argument and it's starting to feel overused and, frankly, not indicative of reality.
I find that there's a lot of resume padding when it comes to the web industry and "modern stacks" these days. My job involves managing a large monorepo, and I'm in contact with dozens of projects and teams daily. From my experience, I found that when people actually inherit someone else's React thing, it typically agonizes a slow death with minimal amounts of updates until it finally gets thrown out or rewritten.
Also, I've seen some seriously over-engineered stuff that honestly just boiled down to 95% static content and a handful of dynamic elements (e.g. some form validation). Many of these don't need to be a SPA and often can be architected to require very little JS in the first place.
When people say they use vanilla js, the assumption should not be that they have the same amount of JS code that a React codebase does: it typically means that the vast majority of what would be React code is simply not written in JS at all.
I'm not a fanboy of frameworks, but I would not touch a project without some "published framework".
If you DON'T pick/use a framework.. you STILL are using a framework. Just a framework that YOU invented, that doesn't come with documentation, examples, best practises and 1000 questions on StackOverflow. Ever worked on a JQuery project with more than 3 people or one that took longer than 6 months !? Its a nightmarish mesh !! Since there are no std ways todo stuff.
Thats what the frameworks gives you, documentation, examples, Q&A and std practises (some are even best practises).
I'm sure once you start asking around for the experts and their opinion they will tell you why the framework xyz is wrong but honestly at least everyone on the team and the poor consultants that comes after you, can be "consistently wrong" and know where to jump into this project.
Rant-over sorry :) But "VanillaJS and/Or Clean Jquery" Yea no just no.
Php: Yea its a mess but a simple mess to get going :) As per first comment.