32 ms·

Hopefully this turns out well for the community. Some advantages I can see being based on ruby 1.8.7 is that now people will have a specific language to develo

by bugs 17y ago

Hopefully this turns out well for the community. Some advantages I can see being based on ruby 1.8.7 is that now people will have a specific language to develop libraries for, also new people to ruby can have something specific to start with (rather than having to chose between 1.9/1.8). Those that still want to move so quickly can still choose to do so and continue to use and support 1.9 they just might not have the same following as before.

incomethax 17y ago
I really enjoy the speed improvements that 1.9 affords, I can't help but think this will bring back the arguments that Ruby is a slow language simply because the "standard" implementation is slow.
- steveklabnik 17y ago
  Just because 1.8.7 will be 'standard' doesn't mean that MRI has to remain the standard interpreter for it.
  - philwelch 17y ago
    In fact, standardization and a written spec will make it more likely that faster interpreters will be written for it.
deleted 17y ago
[deleted]
- deleted 17y ago
  [deleted]
carbon8 17y ago
I think it's a mistake to believe that this has a big impact on new users or which implementations any of us support in our code. Plus, it's important to note that the current draft spec actually supposedly covers the existing 1.9 implementation and all other existing implementations by excluding features that differ between them. From the Drafting Guidelines (http://ruby-std.netlab.jp/ http://ruby-std.netlab.jp/): Second, we intend that existing implementations such as Ruby 1.8.7, Ruby 1.8.6, Ruby 1.9, JRuby, Rubinius, and IronRuby can conform to the specification without modifying them. There are some features which are not implemented in some of the implementations or are different among the implementations. Those features are excluded from the specification, or described as either "implementation defined" or "implementation dependent."

by bugs 17y ago

incomethax 17y ago

I really enjoy the speed improvements that 1.9 affords, I can't help but think this will bring back the arguments that Ruby is a slow language simply because the "standard" implementation is slow.

steveklabnik 17y ago
Just because 1.8.7 will be 'standard' doesn't mean that MRI has to remain the standard interpreter for it.
- philwelch 17y ago
  In fact, standardization and a written spec will make it more likely that faster interpreters will be written for it.

deleted 17y ago

[deleted]

deleted 17y ago
[deleted]

carbon8 17y ago

I think it's a mistake to believe that this has a big impact on new users or which implementations any of us support in our code. Plus, it's important to note that the current draft spec actually supposedly covers the existing 1.9 implementation and all other existing implementations by excluding features that differ between them. From the Drafting Guidelines (http://ruby-std.netlab.jp/ http://ruby-std.netlab.jp/): Second, we intend that existing implementations such as Ruby 1.8.7, Ruby 1.8.6, Ruby 1.9, JRuby, Rubinius, and IronRuby can conform to the specification without modifying them. There are some features which are not implemented in some of the implementations or are different among the implementations. Those features are excluded from the specification, or described as either "implementation defined" or "implementation dependent."