chewbranca's comments

The only problem with that comparison is the first six example results have nothing to do with "Ruby on Rails".

This graph is biased by the fact that you're searching 3 words versus one. I personally qualify searches with "rails" throughout the day, but hardly ever actually search "ruby on rails". I imagine most other rails devs do as well, so this graph is missing a substantial amount of rails traffic.

As someone who is 6'8", 310lbs and spent 12 hours flying last week, I would have to strongly disagree. Until airlines provide a means of adjusting available room to compensate for height, its not appropriate to charge taller people more at all.

Try: http://beta.manning.com/

Lists all of your ebooks with quick download links and last updated times for meap books. Been using it for a while now with no issues.

Sounds more appealing than "Windows for Submarines" - http://www.strategypage.com/htmw/htiw/articles/20081225.aspx

Alternatively, take advantage of your commute. I switched from driving to public transit and I've found the time can be incredibly productive, as its in between work time and at home family time, which makes it much easier to concentrate on what I need to do.

The issue with that is the ability to disable secure boot is not included in the spec, and therefore is not required by any of the OEMs to include.

Edit: reply to comments on spec and disabling boot loading.

FYI, I haven't read the spec, and I based my statement from the other article on the home page: http://www.theregister.co.uk/2011/09/26/uefi_linux_lock_out_...

The relevant quote is: "Garrett said that Windows 8 certification requires that hardware ship with UEFI secure boot enabled. A feature allowing secure boot to be disabled – necessary to run Linux and FreeBSD on certified systems – is not required for certification."

And further: '"We've already been informed by hardware vendors that some hardware will not have this option," Garrett writes in a flow-up blog post to his original critique of the technology.'

Hrmm... sat here thinking about the question, then thought 'a weather API would be nice, let me see if anyone else already answered that'.. ctrl-f weather.. oh great, the one guy who mentioned a weather API is also from Seattle.

For those looking for more information, check out the specification page which has a nice introduction and more in depth documentation:

http://www.lambdassociates.org/specification/shen_1.7.htm

I agree that the value add isn't significantly high for small cluster type of situations, and I would much rather just have a caching API available that charges on usage and allows you to specify an amount of redundancy.

However, the automatic failovers is very nice. From Vogel's blog: "Amazon ElastiCache automatically detects and replaces failed Cache Nodes to protect the cluster from those failure scenarios." That is definitely nice.

Elasticache does seem to be sitting in an awkward middle ground between renting of instances and paying for usage in an API.

Edit: after thinking about it more and reading some of the comments, I think an ideal setup would be an API to a memcached like datastore with buckets so I can specify max-size, redundancy, expiration methods, etc on a per bucket basis. Even nicer setup would be all of that plus redundancy and HA across availability zones and regions.

Nice trick using a proxied netcat command to forward ssh connections through a server. Was not aware of that, and I spend a lot of time running through a front ssh server, thanks!

For those of you just getting into this book, there is also a great course with video lectures up on MIT's OCW site: http://ocw.mit.edu/courses/electrical-engineering-and-comput...

Focused on javascript, but this is a great introduction to closures: http://jibbering.com/faq/notes/closures/

A great way to dive into functional programming is to read the book that this topic discusses.

To clarify for the downvoters, I'm talking about this in the context of CouchDB, which I believe was a fair assumption to make seeing as Damien Katz is one of the principle people involved and it was announced today at CouchConf.

In CouchDB, running a filter on top of view results is something you can only do in list functions or client side, so I am very curious to see how they incorporate this into CouchDB.

The data is not necessarily unstructured, it just doesn't have a strictly inforced schema. So I'm very intrigued by this if they're adding it as a layer on top of CouchDB views. If they are, you could use your views to selectively filter on documents with a known structure, and then safely operate across a subset of your docs with unql. We'll see where they go with this though.

It can be a tricky problem because you have a 1 to 1 correspondence of hacker news posts to web pages, so you can't combine articles from multiple sources into a single discussion.

Its a design choice that has pros and cons. One related problem that I find more relevant than multiple posts from multiple sources, is the life time of posts on hacker news. Once something fades from the front page, it falls into irrelevance aside from reference for google search. Which is again a design choice, and I'm not sure the future goals of the site are to support long term discussion.

I keep seeing these (admittedly cool) redis based job queues popping up for different languages, such as resque, pyres, now kue, etc, however I'm disappointed to not see any standardization among them. Obviously they're different projects created by different people, but it would be great to have a common protocol amongst them, especially since they're all just json based messages.

I want to be able to use a job queue as a standard way to communicate between various language backends, so I can use different tools for different jobs. I've started looking into beanstalkd as it has an impressive list of client libraries: https://github.com/kr/beanstalkd/wiki/Client-Libraries.

I'm curious to hear if anyone has any thoughts/experiences/recommendations on using open source job queues to facilitate background processing between different languages and backends. I'm already using redis and resque, something like rabbitmq is overkill, and I just started looking into beanstalkd.

Ahhhh that would be why, I didn't notice the 'future' billing change that is supposed to happen tomorrow.

I'll edit my original post to clarify.

On a more serious note, thanks for the great work Heroku! Very excited to see you guys turning into a generic service platform with a strong API based addon presence.

Following the steps in that gist, I have a heroku clojure app up that just created an invoice line item for 1 worker. It was only for a few minutes, but I definitely just got charged for it.