Debriefing of ruby standardization

In this week, Debriefing of Ruby standardization has been held. I try to write some summaries.

• Ruby has been standarized as ISO/IEC 30170 in April, 2012.
• When Matz started creating Ruby as "hobby program" 20 years ago, he had never thought "Ruby becomes any kind of standards" and "Ruby does not fit any kind of standards".
• ISO advantages
  • Public purchase projects need programming language is standardized.
  • Projects about embedded system want programming language is standardized.
  • Sales talk at business : "Ruby is ISO-standarized!" :-)
• Ruby is the first "ISO-standardized" programming language born in Japan.
• Ruby is also the first "ISO-standardized" programming language worked by Japanese standardization team.
• At first, JIS-standardized in Japanese (March, 2011), at second, JIS-standardized in English (July, 2011), at last, ISO standardized, so that Ruby is also the first programming language from JIS-standardization.
• Ruby standardization is based on Ruby 1.8.7.
• Ruby standardization contains common parts between Ruby 1.8.7 and Ruby 1.9.x.
• Ruby standardization does not contain any parts not-compatible with Ruby 1.9.x.
• So that current Ruby standardization is not "full set", that is just "fast track procedure".
• mruby is almost based on Ruby standardization, without Regexp, MatchData, File and IO.
• Notably, Ruby is still community-based programming language while Ruby is standardized.
• Tasks after ISO-standardized
  • Refine standards as "full set"
  • Refine standards compatible with Ruby 1.9.x/2.0
  • Backport standards from ISO to JIS

And related information:

• mruby is for embedded domain - excepting any real time systems.
• Ruby 2.0 will be released on February, 2013.