@bascule Let me give you a new narrative to hate. Ruby's syntax is nothing special in 2012. In fact, it looks a bit messy.
-
-
-
@KirinDave says the guy whose SOAP integrations were littered with underscores o_O -
@bascule Oh no not UNDERSCORES. -
@KirinDave well, you're the one talking about messy syntax... -
@bascule Yeah underscores are totally on the order of what I'm talking about. -
@KirinDave the equivalent Ruby code (which I was actually writing at the time doing a similar integration) looked a *lot* cleaner, IMO... -
@bascule Ruby's lipstick notwithstanding, its expressive power is _no longer exceptional_ in the production software world. -
@KirinDave no disagreement there - 2 more replies
New conversation -
-
-
@bascule for like the 30th time, we've tried jruby, its still 100x slower -
@capotej the LivingSocial monorail was 100x slower on JRuby too... until I fixed the performance problems. Then it was faster... -
@bascule come work here and move us all to jruby -
@capotej I'm happy at LivingSocial, thanks ;)
End of conversation
New conversation -
-
-
@bascule@headius Tell it to@jolieodell. She wrote the article. -
@obfuscurity@headius it's not@jolieodell's fault. This has been the Twitter "party line" for years: http://www.unlimitednovelty.com/2009/04/twitter-blaming-ruby-for-their-mistakes.html … -
@bascule@headius@jolieodell I'm not saying its her fault. But it's reasonable to ask for external SME opinions. -
@obfuscurity@bascule@headius Sorry, I was briefly covering Twitter's perspective this time. Would you offer a guest post counterpoint? -
@jolieodell@obfuscurity yeah, I'd say ask@headius. Also no worries, that's how everyone at Twitter ha talked about Ruby for awhile -
@bascule@headius I always assumed it's because their scale requirements were so unusual. Anypoops, I'm the letter j @ http://venturebeat.com
End of conversation
New conversation -
-
-
@stuhood thanks to boxed ints/floats, JRuby does poorly on numerical benchmarks :|
End of conversation
New conversation
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.