https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.1q38fj8mz
This article shows that popular classic MVC model does not seem to be the best approach to build many modern web applications.
https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.1q38fj8mz
This article shows that popular classic MVC model does not seem to be the best approach to build many modern web applications.
1 Comment
Tomi Engdahl says:
With the popularity of React and component-based architecture, we saw the rise of unidirectional architectures for managing application state.
One of the reasons these two go so well together so well is that they cover the classic MVC approach entirely. They also provide a much better separation of concerns when it comes to building front-end architectures.
But this is no longer a React story. If you look at Angular 2, you’ll see the exact same pattern being applied, even though you have different options for managing application state like ngrx/store.
There wasn’t really anything MVC could have done better on the client. It was doomed to fail from the beginning. We just needed time to see this. Through this five-year process, front-end architecture evolved into what it is today.
Source: https://medium.freecodecamp.com/is-mvc-dead-for-the-frontend-35b4d1fe39ec#.ec4e8y4bs