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.
Agreed. But to be fair one would have to do the same for Node: add "node" and "nodejs". It'd be tough though, since like "rails" there are multiple contexts the words can be used. This is just one milestone; not meant as an exact comparison.
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.
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.
Many folks can't make that switch (from driving to public transit) because there isn't reliable and/or suitable public transit for that route -- but this doesn't change the point.
Look for housing that is either very close to where you work (remove the commute) OR that's well-placed for a simple and comfortable commute on public transit (try it out a few times, at the times you'd be using it!) where you can also get some side-project work done.
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.'
The ability to disable it is in the spec, but it's not required by the spec. Equally, the ability to override security decisions on a case by case basis is in the spec, but the Microsoft certification requirements forbid it.
Huh, what? The ability of disable secure boot IS in the spec, and it is included in the Samsung tablets that Microsoft got Samsung to make for their developers. How was it implemented if it's not in the spec.
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.
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.
> 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.
Raising the question of why Amazon didn't adapt its S3 API to the task, and then layer an optional memcached-compatible wrapper on top of it.
