41–50 of 155 posts
Neat, I really like the idea of being able to sync local storage with a Couch backend. > Hoodie currently only runs on OS X Oh, a hipster framework.
Ugh, the word 'hipster' should be banished, along with the word 'fanboy'.
Earlier quoted context omitted.
Nothing, all they can do is fuck up their own data.
Which sounds kind of bad, if that is the case. 1. Even if the users are idiots you shouldn't let them ruin their own application experience. 2. I would never put anything remotely connected to security and user privileges in the same storage accessible by users, so I would have to set up a separate service.
2. Security handling is purely server-side. You can’t fake your way without using a proper auth-channel.
Earlier quoted context omitted.
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 bro…
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 st…
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?
I'm a Unix developer and would love to have a play, a little bit disheartening to see that the installation instructions are OS X exclusive.
Hoodie is just Node.js & CouchDB, you should be able to run it without too much trouble. Try to follow the instructions here: https://github.com/hoodiehq/hoodie-app/issues/35 Were happy to help
I see you've already mentioned switching to PouchDB on your backend, and you're already using CouchDB for the cloud, so it seems like you're basically competing straight up against Kanso. So.... How is what you're doing different from what Kanso does? Why should I use Hoodie over Kanso?
I see this code in your docs:
hoodie.account.signUp('joe@example.com', 'secret')
hoodie.account.signIn('joe@example.com', 'secret')
users.create('testuser', 'testing', {roles: ['example']}, function (err){});
session.login('testuser', 'testing', function (err, response){}});
If we take the overall architecture as a given (browser based app, PouchDB or equivalent for local storage, syncing with CouchDB in the cloud, and node workers handling the backend work), what's the focus of Hoodie that sets it apart from Kanso?
(In any case, nice stuff. I think the concept is great, and there's definitely room for several competing frameworks in this space.)
I'm a Unix developer and would love to have a play, a little bit disheartening to see that the installation instructions are OS X exclusive.
Like mentioned elsewhere in this thread, other *nixen support is in the works. Hoodie core is platform agnostic, we just chose Mac as the dev environment because we figured that was what most people use. We are definitely not exclusive and would love to see any help towards getting it run on other systems :)
Unlike a lot of comments here, I don't need to be sold on the concept. As luck would have it, I am actively building an app that runs mostly in the browser using CouchDB, Kanso, and PouchDB. It's a pretty amazing tech stack; I get a local DB in the browser, which I can sync with the main DB in the cloud the client is connected. Plus I get some nice APIs for stuff like sessions, registering users, security, validation…
As far as originality, we choose a different design approach. We want to cater to people who barely get jQuery and give them a tool to build larger apps. We are building the technology downwards from that idea towards the bits and pieces we have.
One of the fun things about Hoodie is that there is nothing technically new in it. Existing ideas and tools are just put together a different way.
I think promising "we want to enable you to build complete web apps in days" might be promising too much. Programming is difficult, there is no silver bullet, and a different data store certainly won't change that. Interesting choice of couchdb. Any reasons for that compared to the alternatives?
In other words, for the very specific problem they're trying to solve, I don't think there ARE a lot of alternatives except "abandon local storage, and work directly against a DB in the cloud".
Earlier quoted context omitted.
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 st…
> 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.
Edit: I take back the MS jab - unnecessary when simply trying to understand something. My apologies
Earlier quoted context omitted.
> Oh, a hipster framework. Never attribute to hipsterism what could adequately be explained with picking priorities :) The hoodie backend works anywhere node and Couch work (anywhere, really), it’s just that the local dev setup with the fancy domains and everything is tailored to Mac OS X. We have Linux support in the works.
Yeah, a hipster framework.