[lnkForumImage]
TotalShareware - Download Free Software

Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Purpose of Ruby 1.9?

Radoslaw Bulat

12/26/2007 8:51:00 PM

First of all I want to thank Matz and Ko1 for yours great work! I
can't say how much thankful I am for Ruby language.

My question is generally to Matz, Ko1 or other Ruby core maintainers.
We have Ruby 1.9 already released. Matz says that it's not stable as
he expected, so it requires some work to become stable. But what
intentions are for Ruby 1.9.x? Is it released mainly for developers
and programmers which are very close to language (language, gem
maintainers) or it's regular release for production usage? Does Ruby
follow unix style for labeling versions? (1.8 stable, 1.9 development,
2.0 stable etc) I've read dissenting opinions of it.

20 Answers

ThoML

12/26/2007 9:41:00 PM

0

> Does Ruby
> follow unix style for labeling versions? (1.8 stable, 1.9 development,
> 2.0 stable etc) I've read dissenting opinions of it.

IIRC this was true for 1.7. I think the "stable" version after 1.6 was
1.8.

Wolfgang Nádasi-donner

12/26/2007 10:30:00 PM

0

tho_mica_l wrote:
>> Does Ruby
>> follow unix style for labeling versions? (1.8 stable, 1.9 development,
>> 2.0 stable etc) I've read dissenting opinions of it.
>
> IIRC this was true for 1.7. I think the "stable" version after 1.6 was
> 1.8.

I'm somehow surprised, because it was named since a long time what is
behind Ruby 1.9.

1) Starting with planned Ruby 1.9.1 Ruby will not follow the even-odd
number scheme, that was followed before. Ruby 1.9.n (n>=1) will be a
stable version, planned for production usage.

2) Ruby 1.9.n (n>=1) contains the ideas from Ruby 2, that are actual
feasible.

3) Work on Ruby 2 didn't start now.

4) Ruby 1.9.0 was released instead of the planned Ruby 1.9.1, because
the trunk was not as stable on 25.12. as everybody wants. It is not
intended as a production version.

5) Ruby 1.9.0 is stable in respect to features, and is from this
viewpoint a reference inplementation, which can be used by developers.

This is what how I understand all the posts an conference videos on the
last year. I hope it is complete an correct (Mats?)

Wolfgang Nádasi-Donner
--
Posted via http://www.ruby-....

Windham, Kristopher R.

12/26/2007 10:39:00 PM

0

in the Desktop reference by Matz, printed in 2002,
he says ..
"Developmental releases of Ruby always have an odd minor revision =20
number such as 1.5 or 1.7.
Once a developmental release is stable and finalized, it's then =20
"promoted" to a stable release. Stable releases always have an even =20
minor revision number such as 2.0 or3.2. Therefore, releases with =20
even subversion numbers are stable releases. Releases with odd =20
subversion numbers are developmental versions..."
I assume this is still the case.
Do not ever use a developmental release for production.
As far as intentions for 1.9.x, I will leave that answer to some one =20
else.

On Dec 26, 2007, at 4:17 PM, Luiz Vitor Martinez Cardoso wrote:

> You are asking very usefull questions! Well... we need wait to someone
> answer ;)
> Regards,
> Luiz Vitor.
>
> On Dec 26, 2007 6:50 PM, Rados=C5=82aw Bu=C5=82at =
<radek.bulat@gmail.com> =20
> wrote:
>
>> First of all I want to thank Matz and Ko1 for yours great work! I
>> can't say how much thankful I am for Ruby language.
>>
>> My question is generally to Matz, Ko1 or other Ruby core maintainers.
>> We have Ruby 1.9 already released. Matz says that it's not stable as
>> he expected, so it requires some work to become stable. But what
>> intentions are for Ruby 1.9.x? Is it released mainly for developers
>> and programmers which are very close to language (language, gem
>> maintainers) or it's regular release for production usage? Does Ruby
>> follow unix style for labeling versions? (1.8 stable, 1.9 =20
>> development,
>> 2.0 stable etc) I've read dissenting opinions of it.
>>
>>
>
>
> --=20
> Regards,
> Luiz Vitor Martinez Cardoso [Grabber].
> (11) 8187-8662
>
> rubz.org - engineer student at maua.br


Rick DeNatale

12/26/2007 10:53:00 PM

0

On Dec 26, 2007 5:39 PM, Windham, Kristopher R. <kriswindham@gmail.com> wrote:
> in the Desktop reference by Matz, printed in 2002,
> he says ..
> "Developmental releases of Ruby always have an odd minor revision
> number such as 1.5 or 1.7.
> Once a developmental release is stable and finalized, it's then
> "promoted" to a stable release. Stable releases always have an even
> minor revision number such as 2.0 or3.2. Therefore, releases with
> even subversion numbers are stable releases. Releases with odd
> subversion numbers are developmental versions..."
> I assume this is still the case.
> Do not ever use a developmental release for production.
> As far as intentions for 1.9.x, I will leave that answer to some one
> else.

Matz announced a change to this versioning policy a few months ago on
the ruby core forum.

1.9 which has been in a state of definitional flux for over a year,
with experimental features being added to the language, then changed
or dropped, was to have become functionally stable yesterday. As I
understand it the intent was that yesterday's release was to have been
1.9.1 instead of 1.9.0, which would have signalled this stability. I
think that the language definition for Ruby 1.9 is now pretty well
fixed, although Matz has reserved the right to make changes in the
case that a major mistake is found.

At the same time he made the remarks about the versioning changes,
Matz indicated that 1.9.1 would still not be production ready and that
the implementation would still be evolving over the next several
months. The intention, as I read it, was to put a stake in the ground
with a definitionally stable 1.9 so that the developers of important
ruby code like Rails, etc. could start developing versions compatible
with the new language.

I'm a little concerned that some folks are jumping on 1.9 as an
immediate replacement for Ruby 1.8, which it isn't.

--
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denh...

Dave Thomas

12/26/2007 11:12:00 PM

0


On Dec 26, 2007, at 4:53 PM, Rick DeNatale wrote:

> I'm a little concerned that some folks are jumping on 1.9 as an
> immediate replacement for Ruby 1.8, which it isn't.

Me too:

http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19rig...

Dave

Rick DeNatale

12/26/2007 11:24:00 PM

0

On Dec 26, 2007 6:11 PM, Dave Thomas <dave@pragprog.com> wrote:
>
> On Dec 26, 2007, at 4:53 PM, Rick DeNatale wrote:
>
> > I'm a little concerned that some folks are jumping on 1.9 as an
> > immediate replacement for Ruby 1.8, which it isn't.
>
> Me too:
>
> http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19rig...
>
> Dave

I just answered a post from someone on the Textmate forum who
installed Ruby1.9 as ruby. Now he gets a syntax error inside textmate
when he tries to run a ruby program, since Textmate uses ruby
internally, and some of that code ran into one of the syntax
incompatibilities.

--
Rick DeNatale

My blog on Ruby
http://talklikeaduck.denh...

Radoslaw Bulat

12/27/2007 12:34:00 AM

0

Matz and others - thanks for answers. It's great news for me. I'm
starting exploring new Ruby features. I love this language! :)

botp

12/27/2007 7:53:00 AM

0

On Dec 27, 2007 7:11 AM, Dave Thomas <dave@pragprog.com> wrote:
> On Dec 26, 2007, at 4:53 PM, Rick DeNatale wrote:
> > I'm a little concerned that some folks are jumping on 1.9 as an
> > immediate replacement for Ruby 1.8, which it isn't.
> Me too:
> http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19rig...

will it be "safe" to say that the baptism of fire for ruby1.9 is
lettting it run/support rails 2.0.2 without errors?

kind regards -botp

Xavier Noria

12/27/2007 8:45:00 AM

0

On Dec 27, 2007, at 8:53 AM, botp wrote:

> On Dec 27, 2007 7:11 AM, Dave Thomas <dave@pragprog.com> wrote:
>> On Dec 26, 2007, at 4:53 PM, Rick DeNatale wrote:
>>> I'm a little concerned that some folks are jumping on 1.9 as an
>>> immediate replacement for Ruby 1.8, which it isn't.
>> Me too:
>> http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19rig...
>
> will it be "safe" to say that the baptism of fire for ruby1.9 is
> lettting it run/support rails 2.0.2 without errors?

Wouldn't that be a Rails goal?

The reason Rails does not run on 1.9 are to my knowledge
incompatibilities, it is not due to 1.9 not being production-ready.
People have been sending compatibility patches to Rails, but work
remains to be done.

-- fxn


M. Edward (Ed) Borasky

12/27/2007 9:29:00 AM

0

botp wrote:
> On Dec 27, 2007 7:11 AM, Dave Thomas <dave@pragprog.com> wrote:
>> On Dec 26, 2007, at 4:53 PM, Rick DeNatale wrote:
>>> I'm a little concerned that some folks are jumping on 1.9 as an
>>> immediate replacement for Ruby 1.8, which it isn't.
>> Me too:
>> http://pragdave.blogs.pragprog.com/pragdave/2007/12/ruby-19rig...
>
> will it be "safe" to say that the baptism of fire for ruby1.9 is
> lettting it run/support rails 2.0.2 without errors?
>
> kind regards -botp
>
>
Well ... *after* it works on RSpec, rcov, flog, heckle, ZenTest, and all
of Ryan Davis' wonderful tools, sure, go ahead and fix Rails. :)