Hacker News Reader

Comment by danso | Hacker News Reader

I haven't had time to look at try out the walkthrough, so here's a kind of dumb question that wasn't answered explicitly in the docs: how does it work with existing front-end frameworks, such as Backbone, Angular, Ember, etc?

I ask this because of the description found on the Github page: https://github.com/hoodiehq/hoodie.js

   hoodie is a JavaScript library that runs in your browser.
   It gives you

      user authentication
      data storage and sync
      sharing
      emails
      and so much more

None of these things are really handled by the client-side frameworks mentioned above, so I'm wondering if Hoodie is basically drop-in easy for existing projects.

View on HN

at first, Hoodie is just a Store for data. So instead of Backbone, Angular etc storing their data via AJAX on a server, or in LocalStorage, we can very simply build adapters for all of the MV* frameworks to use Hoodie as their store.

This way, you get accounts and data synchronization for free. And offline ;-)

Emails and other future modules like payments are just extensions of the available JavaScript API in the browser.

I have not read any more than the intro linked, but I am kind of "concerned" by the big claims

  Behind the scenes, Hoodie takes care of account creation, 
  email validation and all the boring backend tasks you have 
  to think of.

yeah, but how. You still need to do account creation, even if you are storing the hoodie-account-object locally in some fashion.

Am I being dense, or is this like a nice client framework that still needs to talk AJAX to the backend, so still needs to allow oAuth, so still needs to change code if the API changes, and so on.

"We just want to make apps, and add billing by Monday" is a bit worrying as a goal to me...

edit: oh, so this stubs out the server side at the client ? It seems like the same amount of work to keep backbone models in synch with the server as it does to keep hoodie? What do I gain?

> yeah, but how.

Hoodie comes with a backend that does all that stuff that can only be sensibly done server-side for you.

> edit: oh, so this stubs out the server side at the client ? It seems like the same amount of work to keep backbone models in synch with the server as it does to keep hoodie? What do I gain?

@gr2m can you take this one?

  Hoodie comes with a backend that does all that stuff that 
  can only be sensibly done server-side for you.

wibble? I run your client and your server and talk to the stubs both ways? Why? Sounds like Microsoft.

Edit: I take back the MS jab - unnecessary when simply trying to understand something. My apologies

Yeah, we are basically copying Microsoft.

Edit: No harm done :)

A lot of my Angular code is glue for the backend, so this would be an absolute godsend.

I've made a backbone adapter a while a go: https://github.com/hoodiehq/hoodie.js/blob/master/stuff/back...

shouldn't be hard to make one for Angular. Happy to help

I'm looking for someone to translate this into an angular adapter and combine it with Yeoman's 1.0b4's AngularJS generator, among other things to test out hoodie. If you were already going to do it, might as well do it sooner than later and get payed for it! :-)

I posted the job on Elance, Freelancer, and Odesk if anyone is interested.

Elance: https://www.elance.com/job/40077787/proposals Freelancer: http://www.freelancer.com/projects/Javascript-Software-Archi... ODesk: https://www.odesk.com/jobs/Create-Hoodie-AngularJS-adapter-w...

Get in touch at twitter.com/gr2m if you don't find anyone by end of April. I'll do it for ya. You can donate the money

Reply on news.ycombinator.com