I’ll try to explain this more clearly for you
most of the methods I write for my collections benefit from client-side simulation through isomorphism. These are the 80% I talked about.
The other 20% of cases (I regret describing these habits with percentage) are situations where I want to use methods exclusively on the client or the server.
It is incredibly easy to move files, methods or even collections from server, maybe to client, and maybe to both (as outside of
/server) - simply because Meteor is cleverly built to have shared API’s for this stuff no matter what part of the environment you need your collection in. With the work put into having shared API’s between the client and the server, it would almost seem absurd to not reap the obvious benefits, which include client-side simulation (or optimistic UI) for methods.