tag:blogger.com,1999:blog-5419182.post74313311577101095..comments2009-12-22T07:08:56.105-08:00Jimmy Schementihttps://profiles.google.com/116380716127564408544noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5419182.post-82776161404657363252009-12-22T07:08:56.105-08:002009-12-22T07:08:56.105-08:00Totally agree that all implementations of Ruby should aim for the latest 1.9.x spec. As you say, Rails 3.0 (which interests me as a current Merb developer) is targeting 1.9, and there's no point at all in a Ruby implementation which can't run Rails :)Mark Rendlenoreply@blogger.comtag:blogger.com,1999:blog-5419182.post-83271206565481256672009-12-12T14:03:15.618-08:002009-12-12T14:03:15.618-08:00Wish I could have attended. I fully agree wIth you on focusing on 1.9 over 1.8. Not being able to use the latest Rails is going to hinder interest. Glad to hear you are thinking similar thoughts.blowmage.comhttp://blowmage.com/noreply@blogger.comtag:blogger.com,1999:blog-5419182.post-77195774714107758082009-12-09T06:36:39.723-08:002009-12-09T06:36:39.723-08:00I agree. Microsoft needs to support 1.9 compatibility sooner than later. Waiting just puts the project farther behind.Greghttp://www.blogger.com/profile/08140166548936829517noreply@blogger.com