[benatkin]

Where do you draw the line? I find using the same term just barely acceptable right now. If ruby was as hot as it was three years ago, maybe I wouldn't. http://www.indeed.com/jobtrends/q-rails-q-ruby.html?relative...

[heartbreak]

Wow three whole years ago? Pack it up ladies and gentlemen we're heading to the Ruby funeral. Sorry for the snark, but tens of thousands of developers are using the real Rack every day. It's a mature component in widely used web frameworks.

Next up a JavaScript framework called Rake because who uses Ruby anymore.

[ddollar]

We picked Rack because we like the conceptual analogy. The naming conflict is unfortunate but there are a limited set of good words available. We hope that context will make the meaning clear.

Thank you for commenting :)

[jhall1468]

3 years is a life time in web dev.

More importantly, who cares? It was a common 4 letter word used to describe an item that holds stuff a hell of a long time before it was a Ruby thing.

Ruby programmers are a... dedicated bunch.

[vidarh]

Those spikes are curious, so let's add a couple of other languages:

http://www.indeed.com/jobtrends/q-rails-q-ruby-q-javascript-...

Seems like this is likely to reflect something other than changes in language popularity. Frankly the data doesn't seem very interesting without correcting for other factors such as total volume of jobs.

Overall, Ruby looks pretty much as popular today as 3 years ago to me from that data, though perhaps with Rails in a downwards trend (awesome - I love Ruby, but finding Ruby work that doesn't imply Rails is harder, and I don't like Rails).

But it's besides the point anyway. I simply explained why someone mentioned Rack, I don't particularly care either way (probably because I don't really care about Convox Rack - I'd never use a single vendor solution like this, and haven't exactly hidden how overpriced I find AWS in past comments).