From: Phillip Gawlowski Date: 2008-05-09T00:09:27+09:00 Subject: Re: Ruby has to be interpreted line by line in runtime, does this affect Ruby's execution efficiency badly? -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Robert Dober wrote: | On Thu, May 8, 2008 at 2:55 PM, Vidar Hokstad wrote: |> On May 8, 1:27 pm, Ron Fox wrote: | |> Ruby _is_ particularly bad in this respect though. Unfortunately a lot |> of this |> is tied to what makes Ruby pleasant to use. | | I am not that sure about this, maybe we might call Ruby challenging | rather than bad and we will see Ruby implementations being quite fast | in the next of couple of years, I am quite confident that YARV and | JRuby will be quite fast but I do not count out the other | implementations as Rubinus or Iron Ruby... JRuby already beats MRI in a lot of cases, and it isn't even fully optimized yet. And it offers JIT compilation, so after a warm up phase, Ruby should be snappy (for large values of 'snappy'). I expect that we see similar results with IronRuby and, eventually, YARV. Dunno about Rubinius, though. That might go through some extra effort, as they implement the core lib in Ruby (the VM's in C, AFAIK). - -- Phillip Gawlowski Twitter: twitter.com/cynicalryan Blog: http://justarubyist.blogspot.com Youth is a period of missed opportunities without the glory of knowing what ~ was missed. ~ -- Cyril Connolly, "Journal and Memoir" 1983 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkgjF50ACgkQbtAgaoJTgL9P0wCfQZkGGCm8sjBbvPvcAnp8taEc Y/sAniqYcyoeiH0U5/y8fc6YAh8AxF0z =LdEU -----END PGP SIGNATURE-----