Preface: Not a Meteor Expert. Please comment with improvements.
Paraphrasing philosophy:
- Hoodie, Look ma! No Backend.
- Meteor, Backend Power on the Fronend.
A couple of high-level observations:
- Hoodie empowers UI/UX people to build full apps without any backend experience or backend experts.
- Meteor empowers developers build apps faster.
- Hoodie focusses on frontend APIs that are hooked up to a generic backend.
- Meteor brings backend APIs to the browser.
- Hoodie is offline-by-default and mobile friendly by treating in-browser-storage as a first class citizen and using asynchrnous, on-demand data exchange, that is real-time when network is available.
- Meteor focusses on always-on real-time networking between client and server.
- Hoodie stops shy of where jQuery, Backbone, Ember, Angluar and friends start. You can pick your preferred frontend stack.
- Meteor comes with a frontend framework. (might be compatible with others, lacking expertise here)
- Hoodie uses CouchDB in the backend for data reliablity and sync.
- Meteor uses MongoDB.
- Hoodie uses NPM for modules.
- Meteor has a custom package manager.
- Meteor has been public for about a year, with a great community, VC funding and all.
- Hoodie is newer and still in developer-preview, but starting to attract interest, contributors and some sustainable business already.
Similarities
- Open Source Licenses: MIT (Meteor), Apache 2.0 (Hoodie).
- Full JS Stack, browser in the front, Node.js in the back.
- Fast prototyping of apps.