Seems to be a scenario here that is missing.. Eg Umbraco is a CMS that allows for scripts and css to be updated via the backoffice.
So frontend were now missing a filewatch/rebuild to combine and minify if one of the scripts/css is changed by an editor in the backoffice?
But maybe this is now down to the starter kit to provide something? (and it was just nice that the backoffice runtime minification engine could be used frontend)
Prob a different discussion here.. but over time UmbracoCMS has grown up, shall we say, to require this developer pipeline of needing to now have to build and deploy. When I first started using v4 the beauty of UmbracoCMS was that as a dev with very limited experience I could install umbraco on a server and just use the backoffice to do lots of backoffice things without requiring anything other than the backoffice and ftp. 
I wonder if we’ve lost that simplicity along the way?