If I understand the situation correctly: Rails applications benefit from batteries included boilerplate because Rails "owns" the whole stack. "Modern" (contem

If I understand the situation correctly: Rails applications benefit from batteries included boilerplate because Rails "owns" the whole stack. "Modern" (contemporary?) JS applications benefit from separation of concerns, and flexibility because each layer is interchangeable. So how do we make this better? We can't reasonably split Rails up to match the benefits of JS. The obvious (naive?) solution is to provide a protocol that JS layers can follow. Specific packages/layers can decide to provide the protocol which makes them interoperable. The developer may then pick and choose, knowing that if they choose packages that comply with the protocol, they can use the "batteries included" features. It would be fairly trivial to identify the major features that most apps reimplement. Getting it all to play well together would not be as easy. As the OP described, I think Meteor was a great platform, but had some fatal flaws. If "Meteor-the-company" was "Meteor-the-protocol" I think we would have been in a much better position.