It's prediction method is pretty accurate on timing when you should hold off/when you should buy tickets, and how ticket prices are distributed throughout the year. It also compares to the other budget travel sites (Hotwire, etc.).
I'd expect IE is filter through for the next year as corporations and consumers update.
More importantly, education. Millions of PCs will get this browser, and as Firefox continues it's long hike towards being resource intensive and leaky, Google Chrome and others will seem an even better idea.
Empirically, the Ruby is far from death. There is an active community, more publications than before, and an array of frameworks (Sinatra, Rhodes, RoR) to choose from. Saying Ruby is dying is like looking at a single tree in the forest, noticing it's diseased, and claiming the entire forest will fall to that disease.
Also, it's being forked for individual reasons, like Ruby Enterprise, thanks to sites like github.
There's less people writing ruby code. Both in the interpreter itself, and for open source projects using ruby. You can see on that page a graph showing less people are writing ruby code too.
It's prediction method is pretty accurate on timing when you should hold off/when you should buy tickets, and how ticket prices are distributed throughout the year. It also compares to the other budget travel sites (Hotwire, etc.).