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.'"
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.
...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
Does anybody use Ruby (or Ruby on Rails) as the primary language for big-time software projects? Can we name a few that everybody should recognize?
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
Erlang on the backend and RoR on the frontend, actually.
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.