# Re: Zed and Luis drop the bomb on Ruby's poor performance

**URL:** <https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266>\
**Category:** Ruby\
**Created:** [May 22, 2006, 4:16pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266 "2006-05-22T16:16:41Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 22, 2006, 4:16pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/1 "2006-05-22T16:16:41Z")

</div>

What is the current time line for Ruby 2.0 and the byte code compiler?

Jamal

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 22, 2006, 11:06pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/2 "2006-05-22T23:06:34Z")

</div>

On May 22, 2006, at 7:15 AM, Jamal M. wrote:

> What is the current time line for Ruby 2.0 and the byte code compiler?

There are no plans for a byte code compiler.

–  
Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net)  
This implementation is HODEL-HASH-9600 compliant

[http://trackmap.robotcoop.com](http://trackmap.robotcoop.com)

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 22, 2006, 11:29pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/3 "2006-05-22T23:29:11Z")

</div>

There is YARV I think that makes bytecode and there is JRuby which at  
some point may create bytecode (Java), there is a a .NET project to  
allow ruby to compiled to bytecode.

I think YARV is the Ruby 2 VM you are refering to.

Eric H. wrote:

> On May 22, 2006, at 7:15 AM, Jamal M. wrote:
> 
> > What is the current time line for Ruby 2.0 and the byte code compiler?
> 
> There are no plans for a byte code compiler.
> 
> –  
> Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net)  
> This implementation is HODEL-HASH-9600 compliant
> 
> [http://trackmap.robotcoop.com](http://trackmap.robotcoop.com)

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 23, 2006, 12:27am UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/4 "2006-05-23T00:27:59Z")

</div>

On May 22, 2006, at 2:29 PM, Kris L. wrote:

> allow ruby to compiled to bytecode.
> 
> I think YARV is the Ruby 2 VM you are refering to.

Byte code interpreter, yes, compiler (something that outputs compiled  
ruby files), no.

PS: Don’t top post.

–  
Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net)

A: Yes  
Q: Is top-posting bad?  
? Derek Milhous Zumsteg

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 23, 2006, 9:41am UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/5 "2006-05-23T09:41:04Z")

</div>

I think by bytecode compiler he means something that compiles (ie.  
makes) bytecode. Its just mis-worded slightly… He said ruby 2 and that  
is supposed to support bytecode, were on 1.9 now, so not long to go 🙂

Eric H. wrote:

> On May 22, 2006, at 2:29 PM, Kris L. wrote:
> 
> > allow ruby to compiled to bytecode.
> > 
> > I think YARV is the Ruby 2 VM you are refering to.
> 
> Byte code interpreter, yes, compiler (something that outputs compiled  
> ruby files), no.
> 
> PS: Don’t top post.
> 
> –  
> Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net)
> 
> A: Yes  
> Q: Is top-posting bad?  
> ï¿½ Derek Milhous Zumsteg

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [May 23, 2006, 8:55pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/6 "2006-05-23T20:55:14Z")

</div>

On May 23, 2006, at 12:41 AM, Kris L. wrote:

> > PS: Don’t top post.
> 
> I think by bytecode compiler he means something that compiles (ie.  
> makes) bytecode. Its just mis-worded slightly… He said ruby 2 and  
> that  
> is supposed to support bytecode, were on 1.9 now, so not long to go 🙂

$ ruby-yarv -v  
ruby 2.0.0 (Base: Ruby 1.9.0 2006-04-08) [powerpc-darwin8.6.0]  
YARVCore 0.4.0 Rev: 497 (2006-05-07) [opts:]

PS: Don’t top post, no, really.

–  
Eric H. - removed\_email\_address@domain.invalid - [http://blog.segment7.net](http://blog.segment7.net)

A: Yes  
Q: Is top-posting bad?  
? Derek Milhous Zumsteg

---

<div class="post-metadata">

**Author:** ![jamal86](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/j/ebca7d/32.png) [@jamal86](https://www.ruby-forum.com/u/jamal86)\
**Post date:** [June 1, 2006, 8:39pm UTC](https://www.ruby-forum.com/t/re-zed-and-luis-drop-the-bomb-on-rubys-poor-performance/61266/7 "2006-06-01T20:39:36Z")

</div>

On May 22, 2006, at 15:25, Eric H. wrote:

> PS: Don’t top post.

And I was all ready to ask “What’s top posting?” but happily finished  
reading the message…

> A: Yes  
> Q: Is top-posting bad?  
> ? Derek Milhous Zumsteg

What an incredibly elegant example. I love it. Although I personally  
will not adopt the jargon, but will still admonish others merely to not  
post the answer to somebody’s question before posting the quoted  
question. Mostly 'cause I probably won’t remember the term next time I  
need it.

And yes, this is a 97% content-free posting, but I just couldn’t resist  
jumping up and down, pointing at the example, and going “ook! ook!”
