wip

_drafts/2010-12-01-a-scenario-where-tests-facilitate-compatibility-and-communication.markdown

@@ -10,7 +10,7 @@ categories:
 
 ### Short History Lesson
 
-Let's start off with some backstory: there was a time when only one Ruby implementation existed in the world - Matz's own Ruby Interpreter (MRI) written purely in C.  Some time later, JRuby arrived onto the scene, while it was still in its infancy, an announcement was made by [Evan Phoenix](http://twitter.com/evanphx) for a project called [Rubinius](http://rubini.us/).  Rubinius was not just an ordinary Ruby implementation; it was an implementation with a goal to be written in Ruby as much as possible, inspired and modeled off of Smalltalk\-80.  Soon thereafter, [Brian Ford](http://github.com/brixen) joined forces with Phoenix to continue Rubinius development under Engine Yard and to work on a specialized framework called [MSpec](http://github.com/rubyspec/mspec).  This simplistic framework allowed the Rubinius team to create tests of "correct behaviors" found in MRI and to mimic those results in Rubinius.  It was a basic idea designed to measure the progress of the project, and it reaped rewards far more than originally anticipated.  [RubySpec](http://rubyspec.org/) became the name of the collection of "correct behavior" tests and the executable specification for all implementations in the Ruby ecosystem.  By having all implementations follow the standard definition of Ruby (which in this case were MRI and KRI aka YARV), programmers would be able to move around to different implementations with ease and confidence.
+Let's start off with some backstory: there was a time when only one Ruby implementation existed in the world - Matz's own Ruby Interpreter (MRI) written purely in C.  Some time later, JRuby arrived onto the scene and, while it was still in its infancy, an announcement was made by [Evan Phoenix](http://twitter.com/evanphx) for a project called [Rubinius](http://rubini.us/).  Rubinius was not just an ordinary Ruby implementation; it was an implementation with a goal to be written in Ruby as much as possible, inspired and modeled off of Smalltalk\-80.  Soon thereafter, [Brian Ford](http://github.com/brixen) joined forces with Phoenix to continue Rubinius development under Engine Yard and to work on a specialized framework called [MSpec](http://github.com/rubyspec/mspec).  This simplistic framework allowed the Rubinius team to create tests of "correct behaviors" found in MRI and to mimic those results in Rubinius.  It was a basic idea designed to measure the progress of the project, and it reaped rewards far more than originally anticipated.  [RubySpec](http://rubyspec.org/) became the name of the collection of "correct behavior" tests and the executable specification for all implementations in the Ruby ecosystem.  By having all implementations follow the standard definition of Ruby (which in this case were MRI and KRI aka YARV), programmers would be able to move around to different implementations with ease and confidence.
 
 ### RubySpec on Communication