If you work on mostly CMS systems(excluding headless ones) and archaic Server Side Rendering type of applications, then probably don't bother.
But you foresee yourself building server-client decoupled applications, and you want the server agnostic of the consuming client, then probably it makes more sense to use a JS framework to maintain the front end. Frameworks make repeatative tasks easy, and it also becomes easier to maintain the UI in the longer run.
Ultimately, its not a application design question, its a architecture pattern question.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
If you work on mostly CMS systems(excluding headless ones) and archaic Server Side Rendering type of applications, then probably don't bother.
But you foresee yourself building server-client decoupled applications, and you want the server agnostic of the consuming client, then probably it makes more sense to use a JS framework to maintain the front end. Frameworks make repeatative tasks easy, and it also becomes easier to maintain the UI in the longer run.
Ultimately, its not a application design question, its a architecture pattern question.