Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
janl
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
20 ms
·
91.
▲
by
janl
12y ago
Yup :) — We are aiming for the Google Docs sharing model eventually. It is specced out and we are slowly implementing it bottom up based on current use-cases.
92.
▲
by
janl
12y ago
Hoodie does server-side validation of untrusted data.
93.
▲
by
janl
12y ago
They have frontend code that will talk to /singup or whatever the route for creating an account is. Hoodie does nothing different. Thanks for the pointer to Jeremiah, though :)
94.
▲
by
janl
12y ago
Sorry, from “delivering business logic to the client” perspective, Hoodie is no different in concept on that angle. Lots of things are very different, of course :)
95.
▲
by
janl
12y ago
There are API samples further down the main page on http://hood.ie https://github.com/zoePage/hoodie-drawing is an example app.
96.
▲
by
janl
12y ago
Hoodie works no different than Gmail. What’s the worst that can happen there?
97.
▲
by
janl
12y ago
See http://blog.hood.ie/2014/05/talks-about-hoodie-offlinefirst-... for a few pointers :)
98.
▲
by
janl
12y ago
Yeah, it’s a document database, uses UUIDs and revisions for identification and does HTTP-based P2P replication. In Hoodie we abstract that away in a simple to use `hoodie.store` object with the usual `add()`, `update(), `find()`, `findAll(
99.
▲
by
janl
12y ago
Yeah, same here, but it’s a testimonial we received :) Given that Hoodie’s whole focus is on hiding backend complexities, it is not too far fetched, though.
100.
▲
by
janl
12y ago
Hoodie is supported by a bootstrapped company run by the core devs, who put the profits back into Hoodie: http://blog.hood.ie/2014/05/welcome-to-the-neighbourhoodie/ Hoodie also relies on sponsorships, donati
101.
▲
by
janl
12y ago
That is correct :)
102.
▲
by
janl
12y ago
Team Hoodie here. Happy to answer any questions you might have :)
103.
▲
by
janl
13y ago
Worth noting, this is not related to Heartbleed. Find a Heartbleed-related advisory at https://blogs.apache.org/couchdb/entry/couchdb_and_the_heart...
104.
▲
by
janl
13y ago
it’s not quite there yet, but pouchdb.com with pouchdb-server (npm, gh) is the “SQLite to Postgres” in CouchDB terms :)
105.
▲
by
janl
13y ago
CouchDB can’t be bought by Oracle or anyone, since it is run as an independent Open Source project and under an organisation (the Apache Software Foundation) that allows and supports commercial entities contributing, but single vendors can
106.
▲
On aliens – Confessions of a “non-coder” in Open Source projects
(blog.hood.ie)
5 points
by
janl
13y ago
|
0 comments
107.
▲
Show HN: Even Better GitHub Organisations with Ubersicht
(blog.hood.ie)
4 points
by
janl
13y ago
|
0 comments
108.
▲
by
janl
13y ago
you want an app server for that :)
109.
▲
by
janl
13y ago
> The node js addition is to leverage the speed of v8 engine that impacts only the view building time and not much else(I could be wrong though) V8 and Spidermonkey are on par in the way we are using them. Node/V8 just gives us a li
110.
▲
by
janl
13y ago
People were using hoses and lists for things that they should have used an app server for (myself included). As another commentor mentioned, they are meant for interop with legacy systems. That option will remain, but we are likely to depre
111.
▲
by
janl
13y ago
@GrinningFool totally miscommunication, sorry if we cam off wrong. We don’t mean to dismiss the offline metaphors we know from desktop apps, in fact we desperately need to transform them over to predominant app design, especially on mobile.
112.
▲
by
janl
13y ago
We are trying to get people to talk about offline-first app design for when it makes sense. Weather is a great example, being offline could communicated as an error, leaving the user with an abysmal experience. Or some older content could b
113.
▲
by
janl
13y ago
@olegp you remember correctly, I believe you sat on the same table when this happened :)
114.
▲
by
janl
13y ago
Hence my clarification: https://news.ycombinator.com/item?id=6662907 I was trying for a joke (it is still funny in my head), no offence meant.
115.
▲
by
janl
13y ago
Excellent point! I think it is important to derive specs from working implementations and not the other way around ton begin with. But yes, once the spec is in place change gets harder. Bonus points for having a clear versioning / feat
116.
▲
by
janl
13y ago
For the record, I greatly respect Yehuda and have no personal or professional qualms against him :)
117.
▲
by
janl
13y ago
The larger point is that it is worth having multiple implementations of a good idea to choose from, depending what to optimise for.
118.
▲
by
janl
13y ago
My heart goes out to Justine and her courage to talk publicly about this. We are all in her debt.
119.
▲
by
janl
13y ago
Thank you :)
120.
▲
by
janl
13y ago
and the replication model
More ›