> nor is there trivial integration for JS assets/asset pipeline functionality ...WHY would anyone ever want that?! I thought that splitting an app into one fro

> nor is there trivial integration for JS assets/asset pipeline functionality ...WHY would anyone ever want that?! I thought that splitting an app into one frontend-app and one backend-app, each in its separate repository too and runable alone is the very minimum everyone does nowadays. (Yeah, later you may go on and chop the backend into microservices, but for starters you at least keep these two sepratate - why would you want to impose knowledge of Python or Django as requirement for your frontend developers?! Even if you start with a couple full-stackers, you'll want to later be able to hire more narrow focused specialists.)