Well, not every Meteor application in production is just about some like where a wrong number isn’t causing much trouble.
Our app analyzes DNA sequences and makes decisions on the basis of the underlying data. If a race condition occurs and certain data is either stale or not even there, it unfortunately has big implications as it leads to wrong conclusions.
So I think for Meteor apps in production, it very much depends how important the consequences of some stale data would be.
Forgot to mention that we see these race conditions when we run our 1300+ backend tests - two of our test suites show failures regularly when we run them with all other tests but when we run them with .only they deliver correct results. So yes, race conditions happen.