3 ms·
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, e
by lifeisstillgood 14y ago
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?
- janl 14y ago> 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?
- lifeisstillgood 14y agoHoodie 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
- janl 14y agoYeah, we are basically copying Microsoft. Edit: No harm done :)