I think one of the biggest reasons for why it still makes sense to have a monolithic framework is server-aware React components.<p>Most SPAs and React applications re-use tons of stuff like login pages, news feeds, etc. Most of the time, we can re-use some of the frontend UI stuff but end up having to hook it up with our backend manually. But, if we used Meteor, the components can interact with the server side. This allows us to do stuff like use &quot;&lt;Login &#x2F;&gt;&quot; and just have a login page that works, in terms of both frontend and backend.<p>The point is that Meteor&#x27;s goal should be to allow people to build abstractions and re-useable that can step over the client-server barrier. That&#x27;s pretty much only possible when you make assumptions about server and client, i.e. a monolithic framework.