Please create an account to participate in the Slashdot moderation system


Forgot your password?

Slashdot videos: Now with more Slashdot!

  • View

  • Discuss

  • Share

We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).

Programming Ruby

Interview With the Creator of Ruby 89

Posted by Unknown Lamer
from the and-you-thought-java-was-slow dept.
snydeq writes "Ruby creator Yukihiro Matsumoto discusses the past, present, and future of the popular programming language, calling mobile the next target for Ruby: 'I'm currently working on an alternative subset or dialect of Ruby for the small devices. I'm going to make it public early next year. Of course, mobile computing is the way to go, so that's one of the reasons I focus on the Ruby dialect working on the smaller devices.'"
This discussion has been archived. No new comments can be posted.

Interview With the Creator of Ruby

Comments Filter:
  • by AdmiralXyz (1378985) on Wednesday September 07, 2011 @11:43AM (#37327922)
    There's nothing really wrong with TFA, but there's nothing there either. It's so bland. The questions are just "Why did you create Ruby? What's next for Ruby?" I mean, seriously? If you were interviewing someone for a high school newspaper that might be OK, but they really can't do anything better? There's nothing more interesting you could ask Matz?
  • by vlm (69642) on Wednesday September 07, 2011 @12:11PM (#37328416)

    I feel like all the training I did to be able to code games** in a PC is going to be obsolete before I know it.

    Training rapidly becomes useless. Education never becomes useless.

    Memorize how to use a linked list library in Pascal = rapidly useless

    Learn what a linked list is, why and when you'd use it = useful forever

    Also much like human languages (supposedly) the first three languages are pretty tough, but once you learn a bit of ten or so, its pretty simple since all the concepts are the same. The hard part is knowing how to index thru an array without a picket fence mistake and figuring out how to troubleshoot it. The easy part is remembering or googling the syntax.

What is worth doing is worth the trouble of asking somebody to do.