Slashdot Mirror
Interview with the Creator of Ruby
Lisa writes: "Yukihiro "Matz" Matsumoto talks about Ruby's history, the influence of Perl and Python on Ruby, and his new book, Ruby in a Nutshell. In the article he explains: "When I started the language project, I was joking with a friend that the project must be code-named after a gemstone's name (àla Perl). So my friend came up with "ruby". It's a short name for a beautiful and highly valued stone. So I picked up that name, and it eventually became the official name of the language. Later, I found out that pearl is the birthstone for June, and ruby is the birthstone for July. I believe Ruby is an appropriate name for the next language after Perl.""
I looked at Ruby. It is certainly a heartfelt attempt. However, it seems to me that yet another poor communicator has written yet another language.
Not only that, but the Ruby creator has created his own syntax. A new language has one big advantage for the creator: The creator finds the syntax very familiar. Everyone else must struggle.
Links:
The Ruby Home Page
Ruby Language Reference Manual
The Ruby Language FAQ
Programming in the Ruby language by Joshua D. Drake, who is a good communicator.
A Slashdot story and comments: Programming in the Ruby Language
Positive comments about Ruby:
Introducing the latest open source gem from Japan
Thirty-seven Reasons I Love Ruby by Hal Fulton.
Negative comments about Ruby:
As mentioned above, Bruce Eckel does not like Ruby:
"IMO, the Ruby syntax is
Eckel again: "... Python has 10 years behind it and a big, very smart, very active community, a nice number of good books and more on the way, a large set of libraries and a whole process and team in place for developing the language. Recent improvements to the language have outstripped whatever Ruby could offer, I think, and there's currently lots of very good work going on to further improve Python."
For those who would like to quickly see for themselves, there is a section of the The Ruby Language FAQ called Show me some Ruby code
Quotes from Ruby's creator, a Japanese man with an incomplete command of English:
What is the history of Ruby?
"Well, Ruby was born on February 24 1993. I was talking with my colleague about the possibility of an object-oriented scripting language. I knew Perl (Perl4, not Perl5), but I didn't like it really, because it had smell of toy language (it still has). The object-oriented scripting language seemed very promising.
"I knew Python then. But I didn't like it, because I didn't think it was a true object-oriented language -- OO features appeared to be add-on to the language. As a language manic and OO fan for 15 years, I really wanted a genuine object-oriented, easy-to-use scripting language. I looked for, but couldn't find one.
"So, I decided to make it. It took several months to make the interpreter run. I put it the features I love to have in my language, such as iterators, exception handling, garbage collection.
"Then, I reorganized the features of Perl into a class library, and implemented them. I posted Ruby 0.95 to the Japanese domestic newsgroups in Dec. 1995.
"Since then, highly active mailing lists have been established and web pages formed."
--
Links to respected news sources show how U.S. government policy contributed to terrorism: What should be the Response to Violence?
Bush's education improvements were
I am saying that, for me as a native English speaker, the cost of being involved with Ruby is high:
Ruby is a language primarily written and maintained by one person. The author of the language says this in one of the links that I provided. The documentation in English is poor, and, because there is only one primary person working on the language, the documentation is likely to remain poor. That makes a big difference for anyone trying to learn a new computer language, because it vastly increases the cost (in time) of learning.
Also, if there is poor documentation in English, it has been my experience that fewer people adopt a new computer language. English is the world's most common second language. EVERY Japanese student studies English, my Japanese friends say. A friend in Thailand told me that there was a scholarship program to teach computer skills to Thais in Japan. The courses were taught in English.
Try a test: Call the main number of any large German bank. When the operator says hello in German, just start speaking English. You will find that the operator immediately switches to perfect English. If German banks think that communicating in English is important, maybe that is because communicating in English is important in today's world.
If fewer people adopt a computer language, there will be less development. If there is less development, then it may become one of the hundreds of languages that have eventually died. This would increase the cost of adopting Ruby still further.
Poor communication is a BIG issue with open source software, in my opinion (and closed source, too). In my opinion, poor communication is the one big barrier to getting rid of the Microsoft Windows operating system completely. I don't like Windows because I don't like being abused by Microsoft.
My city, Portland, Oregon, USA, has what is said to be the biggest bookstore in the world, Powell's. I went to Powell's technical bookstore and looked at about 20 books on Samba. ALL of them were very incomplete. ALL of them were poorly written.
--
Links to respected news sources show how U.S. government policy contributed to terrorism: What should be the Response to Violence?
Bush's education improvements were