meteor is kindof stuck in DDP+pub/sub+Meteor.Collections. kadira voted for a new datalayer end left the community because meteor could not move forward. mdg itself adapted graphql with apollo but could not make it the default for meteor. The community itself got splitted. Some want to keep the things the way there are and that is ok. But the world keeps spinning and so does the ecosystem. Deprecation of fibers is another nail in the coffin for the classic meteor datalayer.
- meteor adopts or creates a new datalayer and deprecates the classic stack. This has been tried without success
- meteor finds a way to transition the classic datalayer to a async/await compatible variation. This would require to start finding and deprecating code patterns that won’t work without fibers. This could be achieved by forcing promises in some situation. This could be done start to warn now when this is not done. Similarly how react restricts certain patttern in save-mode.
When thinking about it, its probably doable as it only affects server code. The problem is, that much code is shared between server and client.