Support the VRF
09.23.09 - 04:15pm
They want to send a team into Cambodia to document great artists and musicians. It sounds like a pretty amazing project. They just got my $20.
09.23.09 - 04:15pm
They want to send a team into Cambodia to document great artists and musicians. It sounds like a pretty amazing project. They just got my $20.
09.18.09 - 04:12pm
h/t core77.com
It’s amazing how many of these 1993 predictions are just common place today.
09.18.09 - 12:25pm
Seth’s Blog: Things to ask before you redo your website
I think these are perhaps the tenth and eleventh questions you should ask, not the first two. Here’s my list of difficult and important questions you have to answer before you spend a nickel:
09.10.09 - 10:23am
We were seeing a json error in the couchdb logs. Apparently 0.9.1 (because of MochiWeb) doesn’t like certain UTF characters. Unfortunately, this causes replication to totally hang. That’s a bummer. It looks like it’s been patched:
http://issues.apache.org/jira/browse/COUCHDB-333
However, that’s not in the 0.9.1 release.
09.10.09 - 10:21am
If the couchdb book confused you regarding the changes api that supposedly exists:
http://books.couchdb.org/relax/reference/change-notifications
I think that’s a 0.10 release feature (and not yet in 0.9.1). I stumbled upon this API which seems to do something very similar: http://wiki.apache.org/couchdb/HTTP_Document_API?action=show&redirect=HttpDocumentApi (scroll down to “all_docs_by_seq”).
09.09.09 - 09:24am
How to avoid the dog-pile effect on your Rails app | Plataforma Blog
Imagine that in a certain hour, this page on your application receives 4 requests per second on average. In this case, between the first request and the query results being returned, 5 seconds will pass and something around 20 requests will hit your […]
09.04.09 - 11:07am
UPDATE: This is rails-incompatible... which sucks.
Ruby 1.8.6 leaks memory in some surprising places. Even gsub and split on the String class cause some bad headaches. If you're using Haml and 1.8.6 - you are probably in a bit of trouble.
Read more: http://blog.edhickey.com/2008/12/03/memory-leak-in-ruby-186-string-class/
However, simply overwriting the offending methods fixes this memory leak at least. [...]