Interview With the Creator of Ruby
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.'"
Represent, dogg.
Most of those smaller devices don't require subsets of functionality or features. Any general purpose language that doesn't require a super heavy runtime environment or a bazillion linked libraries should get along fine with an API to interact with events generated by the device. See Android, etc.
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?
Dislike the Electoral College? Lobby your state to join the National Popular Vote Interstate Compact.
While I do have Ruby on my N900, I wish him the best of luck in his goals. Between the attacks from the Apple and MS camp on Android and little to no attention being paid to real solutions like MeeGo, all we'll be left with in short order is anti-geek platforms like Windows Phone and iOS, where running things like Ruby (or Python) are expressly verboten.
...but this statement:
> Of course, mobile computing is the way to go
It kind of depresses me for some reason. I am not being ironic, I am serious. I don't know why that makes me feel down.
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.
**or any other desktop coding
Never underestimate the ability of developers to bundle slow scripting libraries and frameworks with their applications.
Obviously, rather than compiling to js and running on the the preinstalled JIT, we should have runtimes for ruby, python, lua, PHP, Perl and every other scripting language under the sun installed on our mobile devices. Makes no sense from an engineering perspective but mercy be that people who are irrationally and emotionally invested in a pet language will STFU!
Mobiles today are about the same power as desktops were when anyone cared about ruby so it should fit well
Makes no sense from an engineering perspective but mercy be that people who are irrationally and emotionally invested in a pet language will STFU!
You seem irrationally and emotionally invested in javascript.
Why does everything have to be on mobile devices. Aren't there better things for language developers to do with their time?
how hard was it to find shoes in the correct color then add all those sequins? I mean, I've seen the pair at the Smithsonian but it's my understanding there were others made as well.
Also, did Dorothy get to keep a pair?
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
I tried to install a program written in Ruby and the experience left me with a very bad impression of the Ruby ecosystem.
I'm a kludgy self taught coder and I just googled for a moment to no avail ... can you help this perma-newb out:
What is a "picket fence mistake"?
Physics is like sex: sure, it may give some practical results, but that's not why we do it.
Can't speak for the GP, but I happen to like JS... I don't see that Ruby really offers much over PERL, except in that neither have had as much effort put into optimization that JS has seen in the past few years. As Node has been increasingly used for highly IO driven workloads, it's being proven to be a good platform for a lot of things. It's the default language of development in-browser (which is arguably where most development happens these days, though not always the most high profile development), and it's natural to want to use a favored language everywhere. JSON has become a preferred transport medium as opposed to XML, and even further pushes to use the language where JSON is native. CouchDB uses JSON for object expression, and JS for application development. MongoDB uses JS for it's default interface, and a binary version of JSON for it's object communication.
I wouldn't say these reasons are irrational at all. I would say that trying to push yet another language on to mobile devices, because the languages already on there aren't the preferred language is fairly irrational. JS is on these devices simply because they interact with the web, which uses JS... any other supported language is because that's the preferred language for the developers of those mobile platforms. Anything more than those two are superfluous and only serve to bloat the underlying platforms.
Michael J. Ryan - tracker1.info
Obviously, rather than compiling to js and running on the the preinstalled JIT, we should have runtimes for ruby, python, lua, PHP, Perl and every other scripting language under the sun installed on our mobile devices. Makes no sense from an engineering perspective but mercy be that people who are irrationally and emotionally invested in a pet language will STFU!
You seem irrationally and emotionally invested in javascript.
If javascript is the only runtime preinstalled, using javascript seems like a pretty rational thing to do to me...
why not, this is second decade of 21st century and gigabytes of storage are cheap. a jvm or dalvik or ruby virtual machine plus a few languages are nothing.
First, let me say I'm a bonafied certified Ruby FREAK (and I've never written a single web app)! So much so, that I spend hours trying to figure out how to bend Ruby into a project instead of finding a more natural tool. My biggest frustration is wanting to distribute a Ruby coded project with GUI to a cross platform audience (often just me). I mean without having to use 4 to 6 different frameworks/IDE's/gems/git-checkouts/etc. I want one "just works", supported, anointed, blessed, Golden way to write a desktop GUI app that I can send to a Windows/Mac/Linux user and they can unzip/untar and run it. That's all I want. Is it just too much to ask?
Ruby is a nice little language. There are a few oddities and the C Ruby interpreter, as Matz admitted, is not very efficient.
Rails, which is what everyone thinks of when they hear Ruby, on the other hand -- well, I'll stay far away from it thanks.
Count me among those developers who never thought that the way to build robust and flexible applications is to first define some database tables, then write a little CRUD code to generate screens. Maybe back in 1989, when SQL databases were new and there were a lot of dumb data entry tasks to automate, and even then, I'm not so sure.
Matsumoto, when you created Ruby you did not have facial hair. But shortly after growing some, Rails came out and changed everything. Now Ruby is popular. Do you feel this is connected to your facial hair?
Democracy Now! - your daily, uncensored, corporate-free