I understand that, which is why I said "ORM(ish)". But a back-office scaffolding would go a long way to move some of us off of Django.
The good side to it being simple to understand and maintain is that you won't pay a lot of debt if you're adding it to your stack.
There isn't a single language that fits all use case perfectly anyway, so we'd have to just go to the "best tool for the job" approach in the meantime.
Care to extend upon why you don't feel go is a good fit for other programming?