I'm Filipe Névola, and I'm Quave's CEO, Developer & Instructor trying to be better every day.
I'm running zcloud.ws. Experience the flexibility and ease of Cloud hosting with amazing support.
tree-shaking is also coming, not working yet branch is here (dead code is already working but tree-shaking itself is in progress) github.com/meteor/meteor/pull/11107
For HMR and tree shaking I'm aware if it, but the fact is that when the article was written it was not available. Which means that I will have something more to praise next year.
As for login with Apple, yes there are about 3 community packages, but due to it being a major OAuth provider like the other officially supported makes that irrelevant as anyone evaluating Meteor without deep knowledge of how things work and of the ecosystem will not see and will not care. I'm looking at this from the marketing and consistency point of view. Apple login is required if you want to be part of the Apple ecosystem, hence it is on par with the other officially supported OAuth providers and should be part of the core Meteor systems. This missing from the docs and guide just encourages the perception that Meteor is outdated, which is my primary interest on this topic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Jan, thank you for this work.
A few comments:
Sign in with Apple: we have Meteor packages up-to-date, supported and working, you can find them here github.com/quavedev/apple-oauth github.com/quavedev/accounts-apple
HMR is coming, the working branch is here github.com/meteor/meteor/pull/11117, btw, I already use this in my projects :)
tree-shaking is also coming, not working yet branch is here (dead code is already working but tree-shaking itself is in progress) github.com/meteor/meteor/pull/11107
And thank you again.
For HMR and tree shaking I'm aware if it, but the fact is that when the article was written it was not available. Which means that I will have something more to praise next year.
As for login with Apple, yes there are about 3 community packages, but due to it being a major OAuth provider like the other officially supported makes that irrelevant as anyone evaluating Meteor without deep knowledge of how things work and of the ecosystem will not see and will not care. I'm looking at this from the marketing and consistency point of view. Apple login is required if you want to be part of the Apple ecosystem, hence it is on par with the other officially supported OAuth providers and should be part of the core Meteor systems. This missing from the docs and guide just encourages the perception that Meteor is outdated, which is my primary interest on this topic.