it is a good separation of concerns, you don't need a specific tool to make an MVC app (although there's plenty of them...), the point is by separating where your data comes from, how you present it and the glue between them separately you make an application that's easy to debug compared to a monolithic model
That’s not a straight answer unfortunately, there’s a lot of different tools and languages for MVC applications. Writing your own application as vanilla as possible is not as straight forward either, and even when it does work you’ll also have to make it scale. Giving the best chance to both ends, a fast and scalable MVC app on a framework, say Rails, and a vanilla JS application written as effciently as possible the only difference would be the amount of work you’re gonna put in, just MHO
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.
it is a good separation of concerns, you don't need a specific tool to make an MVC app (although there's plenty of them...), the point is by separating where your data comes from, how you present it and the glue between them separately you make an application that's easy to debug compared to a monolithic model
There is no performance issue? A MVC app and without MVC are same in loading and fetching data
That’s not a straight answer unfortunately, there’s a lot of different tools and languages for MVC applications. Writing your own application as vanilla as possible is not as straight forward either, and even when it does work you’ll also have to make it scale. Giving the best chance to both ends, a fast and scalable MVC app on a framework, say Rails, and a vanilla JS application written as effciently as possible the only difference would be the amount of work you’re gonna put in, just MHO