Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Hoodie is Open Source and more like BYOBAAS (Bring Your Own Backend As A Service), you can host it yourself, or pay someone to host it for you. You are not beholden to single company’s VCs.

Meteor is about exposing backend and frontend APIs to the browser. Hoodie hides backend complexity as much as it can. The target audiences are very different. Hoodie aims for more frobtendy/designery types, in the future Hoodie definitely wants to reach non-coders as well.

Firebase and Meteor have likely seen more development time, because Hoodie is supported by a bootstrapped company that works on Hoodie part-time and puts it’s profits into future Hoodie development. That way Hoodie moves slower, but Hoodie won’t be at a crossroads when VC funding runs out, or expected growth isn’t big enough.

As far as I can tell, Hoodie’s offline/sync/p2p story is more solid than any other solutions, but then, I’m heavily biased :)

Hoodie’s focus on clean and simple APIs also makes it more easy for beginners.



Firebase does provide robust retry behavior. It tracks data changes, allows explicit online/offline mode, and you can easily write event handlers for sync errors. It also has what looks to me like a much more complete security model.


> Meteor is about exposing backend and frontend APIs to the browser

It is the weirdest description of Meteor I have seen so far.

Meteor is all about helping developers to build excellent web apps with ease and spending less time, not providing APIs.


yeah, my point here is that Meteor gives full-stack (yuck) developers all they need to build quick apps. Hoodie targets UX/Designers/Code-copy-and-pasters.

Full-tack devs will be incredibly quick with Hoodie, like they would with Meteor (or vice versa), it’s just a fundamental difference in design and implementation.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: