5 ms·

Sure, but that's why I mentioned Python: Ruby is only 4 years younger than Python, but I haven't run across that many greenfield projects that involved Python.

• jeffdavis 15y ago
  I think Python developed a little bit more gradually. Ruby was a little slower at first, and then shot up like a rocket. I have no data to back that up, but it certainly seemed to happen that way.
  • gte910h 15y ago
    Ruby exploded really only after the web stuff happened. Python caught on before that.
  • chernevik 15y ago
    Is it significant that Ruby on Rails seems frequently learned "framework first, then language" -- many people first learn Rails, then go to work learning Ruby. Whereas I think frameworks like Django are learned by people already familiar with Python. It's possible that folks can more easily get through the hassles and design questions posed by unit tests with a better grounding in the underlying language.
    • zeemonkee 15y ago
      > Django are learned by people already familiar with Python If only that were true. Like the OP I've been working with mostly legacy Django codebases the last few years and much of the same issues he raises could be applied to those projects as well.
• chc 15y ago
  And they're both older than Java, but you're more likely to see greenfield projects in Ruby or Python than Java because Java gained acceptance much more quickly. The year that the first compiler for a language was written is kind of irrelevant — it's time at certain popularity thresholds that really determines a language's maturity.