MVC had its start in server side rendering. The controller was the entry-point of the HTTP Request (Get or Post) and would, in turn, populate a model (with data), and finally bind the now filled model to the View Template sending back the View with data embedded into HTML statements.
Early Angular did the same thing but on the client side. AngularJS as it was known was a big hit only because of the binding concept. (It had other major architectural flaws).
Today Angular doesn't use the controller rather it uses a router configuration to pass the inbound request (with data or not) to the proper component. The component then only has a View Template, CSS and binding to models of the data.
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.
MVC had its start in server side rendering. The controller was the entry-point of the HTTP Request (Get or Post) and would, in turn, populate a model (with data), and finally bind the now filled model to the View Template sending back the View with data embedded into HTML statements.
Early Angular did the same thing but on the client side. AngularJS as it was known was a big hit only because of the binding concept. (It had other major architectural flaws).
Today Angular doesn't use the controller rather it uses a router configuration to pass the inbound request (with data or not) to the proper component. The component then only has a View Template, CSS and binding to models of the data.