That’s interesting, considering he doesn’t make a point or reference concerning the Meteor hosting product until nearly the end of what is a fairly biased and unsupported [by references or facts] rant about how Meteor doesn’t play well with Node.
Maybe go back and read the article again. Most of the arguments being made are SPECIFICALLY about “breaking the node rules”. There’s a tiny paragraph about Meteor hosting, which is irrelevant c ok considering hosting a Meteor app is as simple as hosting any other node app.
My issue with rants like this is that they are often based in ignorance about how Meteor actually works, and commonly make an argument about how Meteor doesn’t play nice with node, which means they’re by someone who doesn’t actually use Meteor.
I’ve been using node to build applications for a long time. After a simple read of the docs and some third-party sources it was clear what I could use Meteor to scaffold and what came natively.
People don’t seem to understand one simple concept about Meteor: do it the Meteor way if the package you CHOOSE to use is imported via Atmosphere, do it the classic way if it’s NPM, do it the really classic way if manually adding a library. It’s literally that simple.
If you can’t handle some simple guidelines, I’m not sure how you’ve made it through using NPM and “require” and other dependency hell up to this point.