I imagine that the further I would go away from Meteor's style of programming and go to two isolated code-bases (front and back) I would also lose a major part of why one would use Meteor in the first place.
Having tried to build several businesses where I separated concerns across code bases, it always ended up painful in the end for me.
Perhaps being an older (nee wiser?) developer, I could pull the idea off in a more nuanced way, but I bet I will still hit painful points down the road.
