Ruby 1.9.0 came out around the same time as Py3. Ruby 1.9.2 around the same time as Py3.2. They're analogous. Rails 3 shipped at the 3/
-
-
Replying to @wycats
not sure what 30% adoption means, but
is used in way more places than ruby, which is mostly fast moving web dev (rails really)2 replies 0 retweets 1 like -
Replying to @djipko_ns
I think that's a misunderstanding of Ruby's uses. There's Rails (including very old apps) but also Chef, Puppet, QA stuff.
3 replies 0 retweets 1 like -
Replying to @wycats @djipko_ns
it's worth understanding what Ruby did differently, especially before adoption memes set in.
1 reply 1 retweet 1 like -
Replying to @wycats
fair point. Very few would disagree now that py3 prolly "broke" too much. Would not compare the 2 too closely though.
1 reply 0 retweets 0 likes -
-
Replying to @wycats
well apart from different use/deployment, dev cultures are very different, major projects are run differently.
2 replies 0 retweets 0 likes -
Replying to @djipko_ns @wycats
would not bet for example that early django compat would have made as big impact (would have helped for sure)
1 reply 0 retweets 0 likes -
Replying to @djipko_ns
the biggest diff imo is the way string compat was handled. Python went for "hard break"; Ruby took a compatible path.
1 reply 0 retweets 0 likes -
Replying to @wycats
went further and broke more subtle things (for debatable gains) which made compat painful. Diverse audience = less buy-in etc.1 reply 0 retweets 2 likes
yep. To me the amount of breakage (and commitment to compat, esp around strings) is the key comparison.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.