[debaserab2]

> On Sandstorm, we find Meteor apps much easier to package than anything else, because the Meteor tools will output a self-contained app bundle that operates in a consistent fashion for all apps -- thus allowing us to write a common packaging tool that works with all Meteor apps.

What does that mean exactly? I admit, I only kind of know what sandstorm does from it's marketing page (looks like it offers VM's in a more user friendly way with an emphasis on security)

In what way does Meteor allow you to produce quicker or more efficiently than if you went with any standard linux stack?

[kentonv]

The easiest way to understand what Sandstorm does is through the demo: https://demo.sandstorm.io

Try installing Wekan, which is a Meteor-based app.

The thing that makes Meteor easier for us is, as I said, the meteor tools have a command "meteor build" which gathers all of the app's code and package dependencies and puts them into a self-contained directory tree with a start script that is executed the same way regardless of the app. This makes it easy for us to build a tool which turns any Meteor app into a Sandstorm package because the input is in a well-defined, self-contained format.

We are, of course, building tools for other stacks as well. It just takes more work.