I appreciate the separation of concerns. Being able to deploy the front end for template changes without bringing the whole back end application along for the r

I appreciate the separation of concerns. Being able to deploy the front end for template changes without bringing the whole back end application along for the ride is nice. Additionally if your back end also serves an API for a mobile app (or other third parties via a JSON API) it's nice to be able to serve all your clients via the same endpoints as opposed to having and endpoint for JSON and an endpoint for HTML. You can probably do both of those things without a JS front end but I feel it's more common for monoliths to end up in a spot where they _need_ to be broken up rather than having kept everything isolated and clean from the beginning. That's just my experience though, YMMV of course.