# Ruby VM Serial Interview

**URL:** <https://www.ruby-forum.com/t/ruby-vm-serial-interview/93071>\
**Category:** Ruby\
**Created:** [April 27, 2007, 4:24am UTC](https://www.ruby-forum.com/t/ruby-vm-serial-interview/93071 "2007-04-27T04:24:59Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![bbazzarrakk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/47e85d/32.png) [@bbazzarrakk](https://www.ruby-forum.com/u/bbazzarrakk)\
**Post date:** [April 27, 2007, 4:24am UTC](https://www.ruby-forum.com/t/ruby-vm-serial-interview/93071/1 "2007-04-27T04:24:59Z")

</div>

I’ve avoided publicizing this too much in the past, because I wanted  
some time to generate content. However, I’ve just posted the third  
episode in a series of interviews with Matz and Koichi and I think  
it’s becoming quite a resource (thanks to them).

Matz and Koichi are handling their own translation, sharing juicy  
details about the official interpreter, giving hints about future  
plans, and even working in a few jokes. Their effort is way beyond  
the call of duty!

So if you haven’t had a chance yet, take the time to read through  
their answers:

> **[Gray Soft / Not Found](http://graysoftinc.com/articles/2007/02/16/the-ruby-vm-)**
>
> Something has gone wrong.

serial-interview

While you are there, drop some suggestions for the themes of future  
episodes in the comments. Give some questions you would like to see  
answered. I’ll sure use good ideas.

Thanks Matz and Koichi for putting up with my constant nagging  
emails. You two have been too kind.

James Edward G. II

---

<div class="post-metadata">

**Author:** ![bbazzarrakk](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/47e85d/32.png) [@bbazzarrakk](https://www.ruby-forum.com/u/bbazzarrakk)\
**Post date:** [April 27, 2007, 11:17am UTC](https://www.ruby-forum.com/t/ruby-vm-serial-interview/93071/2 "2007-04-27T11:17:15Z")

</div>

Great article. Answered some of my concerns about the new threading  
model. Still a bit worried, especially since they seem to indicate the  
new threading still isn’t truly concurrent.
