janl

17 ms·

121.
by janl 13y ago
By giving each user their own database :)
122.
by janl 14y ago
Yeah.
123.
by janl 14y ago
tl;dr: keeping sockets open only uses very little memory and no CPU when idle. dr: http://jlouisramblings.blogspot.co.uk/2013/01/how-erlang-doe... ff.
124.
by janl 14y ago
Yet again, spot on, thanks @Lazare!
125.
by janl 14y ago
Hoodie can only promise to free you from worrying about the backend by providing one that you can just use. The sharing module e.g. makes heavy use of server side logic and database security and access control features. The Hoodie frontend
126.
by janl 14y ago
As long as the underlying OS can provide file descriptors, CouchDB can handle the concurrent connections through the magic of Erlang, both persistent and shorter lived. There are obvious limits to this, but the Hoodie architecture allows ea
127.
by janl 14y ago
Nailed it!
128.
by janl 14y ago
this is many-client-server. p2p sync enables you opening your Hoodie app on your browser, smartphone and tablet at the same time and make it all work, even when some or all of the devices are offline for short or long periods of time :) &#6
129.
by janl 14y ago
Alright, Team Hoodie is calling it a day. Thanks for the lively discussion and nice feedback, you’ve been great! :) See you again tomorrow CEST. <3
130.
by janl 14y ago
p2p sync is actually a hard problem, you might want to look into the theory :) The value of Hoodie is putting everything together into a way that a jQuery / backbone dev can be productive with. It sounds like you are way more advanced, as s
131.
by janl 14y ago
Yeah, we are basically copying Microsoft. Edit: No harm done :)
132.
by janl 14y ago
Spot on! We stole a lot of ideas from the whole CouchDB application space. @caolan, the Kan.so dev is currently looking into Hoodie as well. As far as originality, we choose a different design approach. We want to cater to people who barely
133.
by janl 14y ago
I’m a Unix dev too, check out my beard in the linked video :D 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
134.
by 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 ba
135.
by janl 14y ago
1. what if that idiot messes with gmail’s web console? 2. Security handling is purely server-side. You can’t fake your way without using a proper auth-channel.
136.
by janl 14y ago
We love Meteor though :)
137.
by janl 14y ago
Nothing, all they can do is fuck up their own data.
138.
by janl 14y ago
Anyone trying for a global maximum will fail :) We designed Hoodie with very few, but very specific use cases, to get the core right. The more use cases we’ll add, the broader it will get, but we have no intention of pleasing everyone.
139.
by janl 14y ago
We have our own little lightweight version of PouchDB that isn’t really a version of PouchDB. It works well for now, but we might migrate to Pouch later.
140.
by janl 14y ago
That’s the Hoodie Spirit <3 :D
141.
by janl 14y ago
CouchDB has validations, we just don’t use them yet, you are welcome to, though :)
142.
by janl 14y ago
> 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
143.
by janl 14y ago
Hey there, other @hoodiehq dev here. Here is a bit longer intro to Hoodie: http://hood.ie/intro.html And a presentation from earlier at @berlinjs including a live demo: https://www.youtube.com/watch?v=X3Ttb0BD8pg
144.
by janl 14y ago
That, and that CouchDB has Sync already figured out. Hoodie didn’t have to invent this. Sync is hard, leave it to the experts.
145.
by janl 14y ago
Yeah, but the departure didn’t have the same effect that the other two had.
146.
by janl 14y ago
PouchDB is on the verge of production ready, building projects with it now is definitely recommended. TouchDB-iOS has shipping apps in the App Store.
147.
by janl 14y ago
Pipi is weewee in German. You pick what the project does :) (OT)
148.
by janl 14y ago
That’s why the article states: > Of course there's a whole bunch of cases I'm happily ignoring, like banking apps, the App Store and pretty much anything with money changing hands.
149.
by janl 15y ago
Yup. We used mochijson2.
150.
by janl 15y ago
Appreciated! :)

More ›