hashbo

8 ms·

31.
by hashbo 15y ago
When the concerns of an individual are focussed so intently on a particular licensing agreement for their works that they lose the perspective that the death of any being is a sad thing. At that point, I’m afraid, I no longer can regard tha
32.
Towards a More Interactive Future(hashbo.posterous.com)
1 points by hashbo 15y ago|0 comments
33.
by hashbo 15y ago
Somewhat amusingly the site is down and we’re left to guess what exactly is 3.5 inches in length ...?
34.
Open America’s Doors to Innovation (EB-6)(huffingtonpost.com)
1 points by hashbo 15y ago|0 comments
35.
46 Hours Gaming and Counting - Support the MegaMan Marathon(megamanforhealing.com)
3 points by hashbo 15y ago|1 comments
36.
Nyan Cat Meets Metal(youtube.com)
1 points by hashbo 15y ago|0 comments
37.
Takin’ VC Money(mashable.com)
3 points by hashbo 15y ago|0 comments
38.
Polyglot Persistence at the NoSQL eXchange London 2011(hashbo.posterous.com)
2 points by hashbo 15y ago|0 comments
39.
Hell Re-Branded(underconsideration.com)
1 points by hashbo 15y ago|0 comments
40.
Sex Appeal: Women Kiss Science Goodbye(futurity.org)
1 points by hashbo 15y ago|0 comments
41.
Jeremy, Call Your Mother - She’s Worried Sick(techcrunch.com)
2 points by hashbo 15y ago|0 comments
42.
Brilliantly Sarcastic Responses to Signs(happyplace.com)
2 points by hashbo 15y ago|0 comments
43.
"Slide to Unlock" your Home with iDoormat(idownloadblog.com)
2 points by hashbo 15y ago|0 comments
44.
by hashbo 15y ago
Hi so I believe you’re asking how does CoW solve consistency issues. This seems to be a recurring theme. I suspect and correct me if I’m wrong this comes from the fact we’re using a non-RDMS database or is it because our actual caching is b
45.
by hashbo 15y ago
Really appreciate the combination of honest and helpful feedback. I will certainly keep doing exactly that :-)
46.
by hashbo 15y ago
Hiya, by an index. The index of course isn’t cached. This model applies equally well to RDBMS as well as non-RDMS systems. You can index which is the most recent version without losing the benefit of caching the data (and potentially it’s d
47.
by hashbo 15y ago
Hi. Yep agreed, I did I believe mention it is most valuable when you have mostly have creates & reads and less updates like in the example of web applications. Of course there are valid in memory level operations, quite famously in the
48.
by hashbo 15y ago
Hey Robert It’s not attempting to give intrigue, I just really haven’t figured the right copy out yet:) Take a look at some more of my blog articles if you like, they explain at least the general idea of what we’re doing. We hope to get ev
49.
by hashbo 15y ago
Absolutely but that is internal to the database and cannot be cached locally. With copy on write semantics being at the application level it means you can cache your data locally and not have to worry about distributed cache invalidation et
50.
by hashbo 15y ago
In theory yes, as it avoids holes in the databases or files used for storage. It’s also the semantics of ZFS - http://en.wikipedia.org/wiki/ZFS
51.
by hashbo 15y ago
Actually a history on a state machine give’s you undo functionality a fairly common pattern, no? You have a stack of states instead of a single state. Trouble is though inter-related states isn’t it :-) things can get messy if you don’t hav
52.
by hashbo 15y ago
Actually copy on write would help you 100% here :-) you just need to take the abstraction a level up. That is mutations to your list would create a new list. The original thread continues reading the stale copy. Therefore reducing consisten
53.
by hashbo 15y ago
So the simple answer is that right now we use a most recent wins strategy because our data is not critical or highly correlated like relational data. For us it’s simple to add at a future date UI features to allow wiki style history. Obviou
54.
by hashbo 15y ago
Fair point, maybe I should have been clearer (and an edit will be forthcoming). My point is that with a version history it’s possible to let the content originator know there is a conflict and allow them to choose which version they wish to
55.
Storage is Cheap, Don't Mutate - Copy on Write(hashbo.posterous.com)
70 points by hashbo 15y ago|31 comments
56.
by hashbo 15y ago
Nice thought provoking article and I can empathise with it. But the title is dangerously misleading IMHO. All feedback is valuable. Decoding it is the entrepreneur’s job - shutting off feedback from your user base can be a quick death march
57.
Tapjoy is looking for a UX/UI/Graphic Designer(sfbay.craigslist.org)
1 points by hashbo 15y ago|0 comments
58.
Amazon escapes the App trap(blogs.computerworlduk.com)
2 points by hashbo 15y ago|0 comments
59.
Adopterr - Beta listing website(adopterr.com)
1 points by hashbo 15y ago|1 comments
60.
by hashbo 15y ago
Hey James, no they aren’t thank God! Otherwise it would also mean the rioters would be armed. It’s bad enough they have makeshift weapons without giving them efficient ones. Once you have armed weapons you can’t make sure only the ‘good guy

More ›