[meteor dev] Ted and Nick found the issue. The site was running in development mode (what you get with "$ meteor run") instead of the direct bundle. That's now fixed.
In development mode, we wrap the whole application inside a monitoring process that includes a proxy server. It's how we support hot code push on a laptop, among other things. But it's not a configuration we intended for production use at scale. We'll think about how to make a clearer recommendation in the docs.
This could be anything, and be completely unrelated to meteor or related in a way that has no bearing on the claims of the article. He did just launch, after all.
I prefer to be interested in things that are ACTUALLY interesting; think Google's Spanner, SpaceX, etc, developed by neckbeards who know what they are doing.
It's generally unkind to come in and trash other peoples' work, especially when it's work that is something designed to help make others' jobs easier and is being open sourced.
Amadeus doesn't know what he's talkin about and hasn't analyzed Meteor. At least add some anecdotes that show you have analyzed the product to give you the right to be so harsh.
Meteor is fantastic and has changed the way we should develop web products forever, and more importantly has opened up a whole new set of expectations for what websites should be capable of. Websites are going to become living breathing creatures as a result. Meteor will lead to a truly collaborative realtime web--one where viewing any website is a group activity, rather than a private one.
In development mode, we wrap the whole application inside a monitoring process that includes a proxy server. It's how we support hot code push on a laptop, among other things. But it's not a configuration we intended for production use at scale. We'll think about how to make a clearer recommendation in the docs.