The problem as I see it is not in whether you divide front and back, but where you divide it and why. First hand experience passed down by my own teachers and

The problem as I see it is not in whether you divide front and back, but where you divide it and why. First hand experience passed down by my own teachers and clearly many others is that that having your business logic mixed in with your UI CODE is a bad idea. A lot of people take that lesson and fuck that message up and here we are. How many times do we write an angular app (using mvc separation). And then connect to an mvc web server framework. And then have a separate backend layer with a database behind that. There is usually many more layers of mvc and separation added in once you look at your class hierarchies and subsystem architectures. Separating is very useful to a point and after that point you are just creating needless overhead. Unfortunately the only sure way to identify that point is by screwing up and rewriting everything