Forward: Drafting a "The Year in Scripting Languages"

Hello,

Is anybody interested in the following and willing to write an article
about the scripting language? I wanted to do it myself, but it’s too
hard for me due to my poor English. Please contact me, or
.

						matz.

------- Start of forwarded message -------
Delivered-To: matz@netlab.jp

···

Date: Wed, 1 Jan 2003 15:28:15 -0500
To: Yukihiro “Matz” Matsumoto matz@netlab.jp
Subject: Drafting a “The Year in Scripting Languages”
From: Mitchell N Charity

Hello,

We met briefly at LL2…

I am coordinating an email with summaries of what various scripting
language communities are up to. Lua, Perl, Python, Ruby, TCL. With
the objective of helping build community and collegiality. I have
commits for Python, TCL, and expect Perl shortly.

Is writing the Ruby section something you could commit to doing?
Or could you suggest someone else appropriate?

My thanks for your help,
Mitchell Charity

Ok, the objective is to put together an email, “The year in scripting
languages (Lua/Perl/Python/Ruby/Tcl)” or some such, with descriptions
from each community, for cross-posting to the languages’ assorted
mailing lists, and a couple of general places like comp.compilers.

The motivation is community building. While each languages’ community
is understandably inwardly focused, I’d like to increase the level of
cordiality. Reduce the negative jingoistic edge which seems to often
flavor discussion. The communities are addressing similar issues,
pondering similar design challenges, but are remarkably unaware of each
other’s work. I’d like to nudge things in a more collegial direction.

The plan is for each language to write up a short blurb. Perhaps a
paragraph each on “summary of what’s happened this year”, “what is/are
something(s) intriguing which happened”, “what are plans for next
year”. And one with links to the language homepage, its software
archive/list, and the web archive of its mailing list(s).

Of course, I’d like to hear about concrete milestones – new features,
significant design work, etc. I’d also be interested in hearing about
significant open issues and challenges – what are the hot topics that
have not been resolved. I’m also interested to hear about how the
user community is evoling and what effect that has on requirements.

The guidelines are that all sections should be interesting and accessible
to three audiences - the language’s own aficionados, people with some
contact with the language but which haven’t been following it, and people
who have not had any exposure. And that the tone should be collegial
rather than competative.

The target deadline is the 9th (thursday).

Earlier rough drafts are welcome, to share ideas among the writers,
and help convergence.

I’ll send out a group email as soon as folks commit.

------- End of forwarded message -------

If you still want to do it, I say go for it. Your English is very
good, and any native speaker could remove the few mistakes you would
make.

Sorry I can’t do it myself. There’s no way I have an adequate grasp
of the issues demanded.

Gavin

···

On Sunday, January 5, 2003, 8:14:48 PM, Yukihiro wrote:

Hello,

Is anybody interested in the following and willing to write an article
about the scripting language? I wanted to do it myself, but it’s too
hard for me due to my poor English. Please contact me, or
.

Yukihiro Matsumoto wrote:

Is anybody interested in the following and willing to write an
article about the scripting language? I wanted to do it myself, but
it’s too hard for me due to my poor English.

Maybe you can write it in Japanese, and then someone else can
translate to English?

I noticed several replies which said that they could not do this - I
probably can’t do the whole thing by the 9th either, so here’s a
suggestion:

What if several of us do this collaboratively? We could set up a wiki
page on the Rubygarden wiki and divide up the tasks and actually put it
together on the wiki.

What do you think?

Phil

In article 1041758064.343233.8931.nullmailer@picachu.netlab.jp,

···

Yukihiro Matsumoto matz@ruby-lang.org wrote:

Hello,

Is anybody interested in the following and willing to write an article
about the scripting language? I wanted to do it myself, but it’s too
hard for me due to my poor English. Please contact me, or
.

  					matz.

------- Start of forwarded message -------
Delivered-To: matz@netlab.jp
Date: Wed, 1 Jan 2003 15:28:15 -0500
To: Yukihiro “Matz” Matsumoto matz@netlab.jp
Subject: Drafting a “The Year in Scripting Languages”
From: Mitchell N Charity

Hello,

We met briefly at LL2…

I am coordinating an email with summaries of what various scripting
language communities are up to. Lua, Perl, Python, Ruby, TCL. With
the objective of helping build community and collegiality. I have
commits for Python, TCL, and expect Perl shortly.

Is writing the Ruby section something you could commit to doing?
Or could you suggest someone else appropriate?

My thanks for your help,
Mitchell Charity

Ok, the objective is to put together an email, “The year in scripting
languages (Lua/Perl/Python/Ruby/Tcl)” or some such, with descriptions
from each community, for cross-posting to the languages’ assorted
mailing lists, and a couple of general places like comp.compilers.

The motivation is community building. While each languages’ community
is understandably inwardly focused, I’d like to increase the level of
cordiality. Reduce the negative jingoistic edge which seems to often
flavor discussion. The communities are addressing similar issues,
pondering similar design challenges, but are remarkably unaware of each
other’s work. I’d like to nudge things in a more collegial direction.

The plan is for each language to write up a short blurb. Perhaps a
paragraph each on “summary of what’s happened this year”, “what is/are
something(s) intriguing which happened”, “what are plans for next
year”. And one with links to the language homepage, its software
archive/list, and the web archive of its mailing list(s).

Of course, I’d like to hear about concrete milestones – new features,
significant design work, etc. I’d also be interested in hearing about
significant open issues and challenges – what are the hot topics that
have not been resolved. I’m also interested to hear about how the
user community is evoling and what effect that has on requirements.

The guidelines are that all sections should be interesting and accessible
to three audiences - the language’s own aficionados, people with some
contact with the language but which haven’t been following it, and people
who have not had any exposure. And that the tone should be collegial
rather than competative.

The target deadline is the 9th (thursday).

Earlier rough drafts are welcome, to share ideas among the writers,
and help convergence.

I’ll send out a group email as soon as folks commit.

------- End of forwarded message -------


“Or perhaps the truth is less interesting than the facts?”
Amy Weiss (accusing theregister.co.uk of engaging in ‘tabloid journalism’)
Senior VP, Communications
Recording Industry Association of America

Hi,

···

In message “Re: Forward: Drafting a “The Year in Scripting Languages”” on 03/01/05, Gavin Sinclair gsinclair@soyabean.com.au writes:

Is anybody interested in the following and willing to write an article
about the scripting language? I wanted to do it myself, but it’s too
hard for me due to my poor English. Please contact me, or
.

If you still want to do it, I say go for it. Your English is very
good, and any native speaker could remove the few mistakes you would
make.

The deadline is 9th. It takes far longer than you thought for me to
write an English article. It’s too short for me.

						matz.

I would be happy to help with that as well.

···

On Sunday, January 5, 2003, at 08:39 PM, Phil Tomson wrote:

I noticed several replies which said that they could not do this - I
probably can’t do the whole thing by the 9th either, so here’s a
suggestion:

What if several of us do this collaboratively? We could set up a wiki
page on the Rubygarden wiki and divide up the tasks and actually put it
together on the wiki.

What do you think?

Phil

[snip]


“Or perhaps the truth is less interesting than the facts?”
Amy Weiss (accusing theregister.co.uk of engaging in ‘tabloid
journalism’)
Senior VP, Communications
Recording Industry Association of America

Hi,

···

In message “Re: Forward: Drafting a “The Year in Scripting Languages”” on 03/01/06, Phil Tomson ptkwt@shell1.aracnet.com writes:

I noticed several replies which said that they could not do this - I
probably can’t do the whole thing by the 9th either, so here’s a
suggestion:

What if several of us do this collaboratively? We could set up a wiki
page on the Rubygarden wiki and divide up the tasks and actually put it
together on the wiki.

What do you think?

How sweet your idea! [ruby-talk:60630] and [ruby-talk:60654] should
be a good start. Could you start the ball rolling, please?

						matz.

I do think that this is something we should do. I can’t do it myself
because I’m just getting started with Ruby.

Matz, your English is pretty good. But if you still feel unconfortable, I
understand. I still struggle with English myself and I often make
embarassing mistakes.

Still, no one knows Ruby as well as you do. Perhaps you could write a
point-form list of things to put down each category and one of the native
speakers who is knowledgeable of Ruby can turn that into a full article.

Could you do that? Would someone volunteer to write the article if Matz
made a list of possible points to mention?

Daniel.

···

Hi,

In message “Re: Forward: Drafting a “The Year in Scripting Languages”” > on 03/01/05, Gavin Sinclair gsinclair@soyabean.com.au writes:

Is anybody interested in the following and willing to write an
article |> about the scripting language? I wanted to do it myself, but
it’s too |> hard for me due to my poor English. Please contact me, or
.

If you still want to do it, I say go for it. Your English is very
good, and any native speaker could remove the few mistakes you would
make.

The deadline is 9th. It takes far longer than you thought for me to
write an English article. It’s too short for me.

  					matz.

The following is my contribution to this project. I think I have
exhausted my capacity to add additional content without doing further
research. I will happily continue to help however I can and can also
contribute to editing and to adding links where needed. Feel free to
edit, rearrange, use, not use, etc.

Ruby.year(2002)

A report by the Ruby community

Introduction

Ruby continued to delight its practitioners and, perhaps, tempt those 

who work in other languages, throughout 2002. Measured by traffic on
the ruby-talk mailing list, more and more people from around the world
are discovering Ruby and the joys it brings to programming. And
visions of the future of Ruby (more libraries, faster execution, more
intuitive interfaces to enhanced functionality) have intoxicated
Rubyists (Rubiots? Rubyphiles? Ruby Miners?) everywhere. The
community itself is such a pleasure to be a part of. In some ways, the
only hard times in the community seem to come from loving Ruby too
much. [Need to add links.]

  1. The release of 1.6.8.

    [I don’t know what’s important to point out here.] [Need to add
    links.]

  2. The release of 1.8 preview.

    [I definitely don’t know what to say here.] [Need to add links.]

  3. Unit Testing with Test:Unit

    The Test:Unit library (http://) is now included in the standard
    Ruby distribution. Test:Unit is an object oriented framework for
    building unit tests. It sports an intuitive interface and rock-solid
    performance. Now, outside-in, method interface oriented and true
    encapsulation design practices are available even to the beginning
    programmer. You will still have to write the tests and write the code
    that passes the tests on your own though. Those currently outside the
    Ruby community also get to skip the extensive, but polite, discussions
    of setup and teardown vs. set_up and tear_down (it’s the former, and
    the discussions are in the mailing list archives, for those with too
    much time on their hands). [Need to add links.]

  4. XML with REXML

    [I haven’t yet used REXML (although I will start fairly soon).]
    [Need to add links.]

  5. Documentation

    Documentation and documentation tools have continued to develop for
    Ruby libraries and applications. However, more and more work is needed
    to keep up with the pace and volume of development efforts. In
    particular, more work is needed on English (and other languages)
    documentation for libraries and applications currently documented only
    in Japanese and/or English. [This needs to be expanded, but I don’t
    really know enough about what’s been done on this.] [Need to add
    links.]

  6. Ruby on Mac OS X.

    Beginning with Mac OS X 10.2 (Jaguar), Ruby is now standard on the
    Mac (along with Perl and Python). __________ has been working on
    RubyCocoa, now at version ___, which makes the Cocoa framework
    available to Ruby. [RubyCocoa is still on my to-do list, so I lack the
    knowledge to adequately address it.] [Need to add links.]

  7. Compiled Ruby and Virtual Machines.

    Matz, the inventor of Ruby, and his unnamed associates (or is it
    co-conspirators?) are working on speeding up the Ruby interpreter
    (while keeping dynamic typing). The choice of virtual machine for this
    purpose is perhaps the most closely guarded secret on the planet and a
    source of almost unbearable suspense for the Ruby community. Is it
    Parrot? Forth? Scheme-48? Only time, and matz, will tell. [Need to
    add links.]

  8. Ruby Books

    2002 saw the publication the English translation of Ruby in a
    Nutshell (by matz), The Ruby Way (by Hal Fulton) and Teach Yourself
    Ruby in 21 Days (by Mark Slagell). Programming Ruby (by Andy Hunt and
    Dave Thomas), known in the Ruby community as the pickaxe book,
    continued to be extremely popular (at least as to the free online
    version) and enormously useful. All who can find and afford a hard
    copy should buy the book, because it is best used open and beside your
    computer (and because sales will encourage more publishers to publish
    more Ruby books).

    • Ruby in Nutshell is by matz, the inventor of Ruby. [I confess, with great embarrassment, that I haven’t read this book.]

    • Teach Yourself Ruby in 21 Days is an excellent book for the
      beginning programmer that also covers more advanced topics such as
      recursion, matrices, binary decision trees and class interfaces. Those
      who are turned off by the title of the book should look deeper (after
      all, you can’t judge a book by its cover or its title). If it helps,
      one might think of it by another title they find more appealing (maybe
      "The Structure and Interpretation of Ruby Programs").

    • The Ruby Way is an outstanding book that covers the Ruby
      approach to solving a broad range of programming problems. Many
      advanced topics are thoroughly covered and the discussions of more
      basic concepts often provide new insights into what is really going on
      in Ruby and in programming generally. It is an intermediate level book
      and is a must-have for Ruby programmers.

[Any others? Also any interesting books in non-English?] [Need to add
links.]

  1. Growing interest in Fox and FxRuby as a desirable Ruby GUI.

    [I don’t know enough about this. Sidenote: I really want to figure out how to get FxRuby working on Mac OS X and will redouble my meager efforts on this.] [Need to add links.]

  2. Ruby and Web Application Development [This section is from Phil
    Tomson with some minor edits by me.]

    Web application development with Ruby is beginning to come into
    its own. Many quality tools are now available and have reached
    milestone stability releases.

    • eRuby provides for embedding Ruby script directly into HTML
      documents, much like PHP, but grants the developer all the power of
      Ruby’s object oriented design.

    • Amrita (http://), an alternative to eRuby, is an HTML/XHTML tag
      attribute-based markup syntax, making for excellent separation of
      content and logic.

    • For accelerated execution, mod_ruby (http://www.modruby.net/),
      the Ruby Apache module, embeds the ruby interpreter directly into
      Apache, much like mod_perl and mod_php, and is quite stable, now at
      version 1.0.2.

    • There are also complete frameworks like CGIKit and ILE
      (http://virtualschool.edu/ile/) to speed development.

    Web development with Ruby is very powerful solution and gives web
    programmers powerful object oriented tools that can be used with
    traditional Perl and PHP scripting or in place of these other tools
    where appropriate. Expect to see many new Ruby-based applications in
    the future! [Need to add links.]

[Ruby on Windows needs to be addressed. I don’t know anything about
this topic]

[The Carrera and Pine tutorials might also be mentioned and linked to
– perhaps in an online resources guide.]

[Also, a section on Perl to Ruby, etc. could also be helpful.]

[Also, a section on using Ruby in an environment along side other
scripting language might be helpful.]

[A coming in 2003 section – FreeRIDE 1.0? others?]

I also don’t think I can write the article because I don’t know what’s
important or know enough about Ruby. However, I irrevocably assign the
following to whoever does write the article (without the need for
credit to me):

  1. The release of 1.6.8.

  2. The release of 1.8 preview.

  3. The inclusion of Test:Unit and REXML in the standard distribution.

  4. Continued work (with more needed) on English (and other languages)
    documentation for libraries and applications currently documented in
    Japanese.

  5. Inclusion of Ruby 1.6.7 in Mac OS X 10.2.

  6. Any developments as to the Windows distribution.

  7. Plans (the details of which are as yet undisclosed) to increase the
    speed of the Ruby interpreter.

  8. The publication in early 2002 of The Ruby Way and Teach Yourself
    Ruby in 21 Days. Any others? Also any interesting books in
    non-English?

  9. Growing interest in Fox and FxRuby as a desirable Ruby GUI.

  10. Ruby and the web developments (mod_ruby, eruby, amrita).

I would also be willing to help whoever writes the article in any way
that I can.

···

On Sunday, January 5, 2003, at 01:16 PM, Daniel Carrera wrote:

I do think that this is something we should do. I can’t do it myself
because I’m just getting started with Ruby.

Matz, your English is pretty good. But if you still feel
unconfortable, I
understand. I still struggle with English myself and I often make
embarassing mistakes.

Still, no one knows Ruby as well as you do. Perhaps you could write a
point-form list of things to put down each category and one of the
native
speakers who is knowledgeable of Ruby can turn that into a full
article.

Could you do that? Would someone volunteer to write the article if
Matz
made a list of possible points to mention?

Daniel.

Hi,

In message “Re: Forward: Drafting a “The Year in Scripting Languages”” >> on 03/01/05, Gavin Sinclair gsinclair@soyabean.com.au writes:

Is anybody interested in the following and willing to write an
article |> about the scripting language? I wanted to do it myself,
but
it’s too |> hard for me due to my poor English. Please contact me, or
.

If you still want to do it, I say go for it. Your English is very
good, and any native speaker could remove the few mistakes you would
make.

The deadline is 9th. It takes far longer than you thought for me to
write an English article. It’s too short for me.

  					matz.

this is a good start, but as you point out someone that has tracked
ruby language changes over the year should make a summary of the
language feature changes. also a summary of the main features of the
language, and preferably not a rehash of something thats been said
before (ie in Ruby book introductions).

also, I’m not sure a Perl to Ruby section is warranted, after all it is
not supposed to be a competitive article. I like how you changed the
language regarding perl and php from phil’s section, that works fine.

again, good draft, this makes me personally at least feel a lot better
that ruby community will send something good to the big article.

digibren

···

On Monday, January 6, 2003, at 12:25 AM, Mark Wilson wrote:

The following is my contribution to this project. I think I have
exhausted my capacity to add additional content without doing further
research. I will happily continue to help however I can and can also
contribute to editing and to adding links where needed. Feel free to
edit, rearrange, use, not use, etc.

Ruby.year(2002)

A report by the Ruby community

Introduction

Ruby continued to delight its practitioners and, perhaps, tempt those
who work in other languages, throughout 2002. Measured by traffic on
the ruby-talk mailing list, more and more people from around the world
are discovering Ruby and the joys it brings to programming. And
visions of the future of Ruby (more libraries, faster execution, more
intuitive interfaces to enhanced functionality) have intoxicated
Rubyists (Rubiots? Rubyphiles? Ruby Miners?) everywhere. The
community itself is such a pleasure to be a part of. In some ways,
the only hard times in the community seem to come from loving Ruby too
much. [Need to add links.]

  1. The release of 1.6.8.

    [I don’t know what’s important to point out here.] [Need to add
    links.]

  2. The release of 1.8 preview.

    [I definitely don’t know what to say here.] [Need to add links.]

  3. Unit Testing with Test:Unit

    The Test:Unit library (http://) is now included in the standard
    Ruby distribution. Test:Unit is an object oriented framework for
    building unit tests. It sports an intuitive interface and rock-solid
    performance. Now, outside-in, method interface oriented and true
    encapsulation design practices are available even to the beginning
    programmer. You will still have to write the tests and write the code
    that passes the tests on your own though. Those currently outside the
    Ruby community also get to skip the extensive, but polite, discussions
    of setup and teardown vs. set_up and tear_down (it’s the former, and
    the discussions are in the mailing list archives, for those with too
    much time on their hands). [Need to add links.]

  4. XML with REXML

    [I haven’t yet used REXML (although I will start fairly soon).]
    [Need to add links.]

  5. Documentation

    Documentation and documentation tools have continued to develop
    for Ruby libraries and applications. However, more and more work is
    needed to keep up with the pace and volume of development efforts. In
    particular, more work is needed on English (and other languages)
    documentation for libraries and applications currently documented only
    in Japanese and/or English. [This needs to be expanded, but I don’t
    really know enough about what’s been done on this.] [Need to add
    links.]

  6. Ruby on Mac OS X.

    Beginning with Mac OS X 10.2 (Jaguar), Ruby is now standard on the
    Mac (along with Perl and Python). __________ has been working on
    RubyCocoa, now at version ___, which makes the Cocoa framework
    available to Ruby. [RubyCocoa is still on my to-do list, so I lack
    the knowledge to adequately address it.] [Need to add links.]

  7. Compiled Ruby and Virtual Machines.

    Matz, the inventor of Ruby, and his unnamed associates (or is it
    co-conspirators?) are working on speeding up the Ruby interpreter
    (while keeping dynamic typing). The choice of virtual machine for
    this purpose is perhaps the most closely guarded secret on the planet
    and a source of almost unbearable suspense for the Ruby community. Is
    it Parrot? Forth? Scheme-48? Only time, and matz, will tell. [Need
    to add links.]

  8. Ruby Books

    2002 saw the publication the English translation of Ruby in a
    Nutshell (by matz), The Ruby Way (by Hal Fulton) and Teach Yourself
    Ruby in 21 Days (by Mark Slagell). Programming Ruby (by Andy Hunt and
    Dave Thomas), known in the Ruby community as the pickaxe book,
    continued to be extremely popular (at least as to the free online
    version) and enormously useful. All who can find and afford a hard
    copy should buy the book, because it is best used open and beside your
    computer (and because sales will encourage more publishers to publish
    more Ruby books).

    • Ruby in Nutshell is by matz, the inventor of Ruby. [I confess, with great embarrassment, that I haven’t read this book.]

    • Teach Yourself Ruby in 21 Days is an excellent book for the
      beginning programmer that also covers more advanced topics such as
      recursion, matrices, binary decision trees and class interfaces.
      Those who are turned off by the title of the book should look deeper
      (after all, you can’t judge a book by its cover or its title). If it
      helps, one might think of it by another title they find more appealing
      (maybe “The Structure and Interpretation of Ruby Programs”).

    • The Ruby Way is an outstanding book that covers the Ruby
      approach to solving a broad range of programming problems. Many
      advanced topics are thoroughly covered and the discussions of more
      basic concepts often provide new insights into what is really going on
      in Ruby and in programming generally. It is an intermediate level
      book and is a must-have for Ruby programmers.

[Any others? Also any interesting books in non-English?] [Need to
add links.]

  1. Growing interest in Fox and FxRuby as a desirable Ruby GUI.

    [I don’t know enough about this. Sidenote: I really want to figure out how to get FxRuby working on Mac OS X and will redouble my meager efforts on this.] [Need to add links.]

  2. Ruby and Web Application Development [This section is from Phil
    Tomson with some minor edits by me.]

    Web application development with Ruby is beginning to come into
    its own. Many quality tools are now available and have reached
    milestone stability releases.

    • eRuby provides for embedding Ruby script directly into HTML 
      

documents, much like PHP, but grants the developer all the power of
Ruby’s object oriented design.

 *	 Amrita (http://), an alternative to eRuby, is an HTML/XHTML 

tag attribute-based markup syntax, making for excellent separation of
content and logic.

 *	 For accelerated execution, mod_ruby (http://www.modruby.net/), 

the Ruby Apache module, embeds the ruby interpreter directly into
Apache, much like mod_perl and mod_php, and is quite stable, now at
version 1.0.2.

 *	 There are also complete frameworks like CGIKit and ILE 

(http://virtualschool.edu/ile/) to speed development.

 Web development with Ruby is very powerful solution and gives web 

programmers powerful object oriented tools that can be used with
traditional Perl and PHP scripting or in place of these other tools
where appropriate. Expect to see many new Ruby-based applications in
the future! [Need to add links.]

[Ruby on Windows needs to be addressed. I don’t know anything about
this topic]

[The Carrera and Pine tutorials might also be mentioned and linked to
– perhaps in an online resources guide.]

[Also, a section on Perl to Ruby, etc. could also be helpful.]

[Also, a section on using Ruby in an environment along side other
scripting language might be helpful.]

[A coming in 2003 section – FreeRIDE 1.0? others?]

links.]

FWIW, The Ruby Way was translated into Japanese in late 2002. I’ve been
meaning to announce that for whoever’s interested. Guess I’ll do it formally
soon.

Might be worthwhile to mention the articles on Ruby – a search
of the ML should turn up all of them (for example, the Ruby/Cocoa
piece in Dr. Dobbs, Mike Stok’s piece in that Perl publication,
etc.).

Also mention the second annual Ruby Conference in Seattle in November.

Hal

···

----- Original Message -----
From: Mark Wilson
To: ruby-talk ML
Sent: Sunday, January 05, 2003 11:25 PM
Subject: Re: Forward: Drafting a “The Year in Scripting Languages”

[Any others? Also any interesting books in non-English?] [Need to add

Mark Wilson wrote:

The following is my contribution to this project. I think I have
exhausted my capacity to add additional content without doing further
research. I will happily continue to help however I can and can also
contribute to editing and to adding links where needed. Feel free to
edit, rearrange, use, not use, etc.

This looks great so far. Like some others on the list, I’d like to help
out if needed. I just checked the Ruby Garden and it doesn’t look like
anyone has Wikified this yet – should I go ahead and do that or have
you guys already got a working document in place somewhere else?

– Lyle

Ruby.year(2002)

A report by the Ruby community

Introduction
[…]

I’m posting this late, and I also didn’t see the wiki page because I’m
reading the messages at home, so feel free to disregard this opinion.

I don’t think that is what was requested. That article seems like a company
advertising pamphlet to me, and I think the idea was a more informal note
about what happened to the Ruby language and community during the last
year, and not to the Ruby “product”.

Ok, anyway, here is my contribution of what happened during 2002, that I
remember and consider noteworthy:

  • RDoc was introduced and now is the de facto standard documentation system
    (and soon the official one)
  • The Ruby Weekly News started (or consolidated, if they started in 2001)
  • Ruby lacks class local and block local variables. How to add them to the
    language in a coherent, elegant (?) and non-breaking-old-code way (I
    think this was the main issue of the year)
  • Gateway list-newsgroup. Message traffic multiplied. Some other, specific
    lists created
  • Various projects to create a repository of ruby packages and automatize
    installation started. rpkg, raa-install, some merge with CPAN. Nothing
    decided yet, but the need remains.
  • Some job offerings requesting Ruby programmers appear in newspapers

And some others that I will remember when I send this message :).

In brief, I think 2002 was a pivotal year for Ruby and its community. In
2001 it was still small (or medium). By the end of 2003 it will be big.
Maybe not as big as the Perl or Python ones, but sufficiently big that some
issues should be settled by then. 2002 was the transition year and raised
awareness about that issues (like repositories, installation and language
semantics [I should think of other issues…]).

Hope this helps and sorry for my English.

Here’s my contribution to the article. Please edit and improve!

  1. Ruby and the web developments (mod_ruby, eruby, amrita).
Web application development with Ruby is beginning to come into its own. Many 

quality tools are now available having reached milestone stability realeases.
eRuby provides for embedding Ruby script directly into HTML documents, much
like PHP, but grants the developer all the power of Ruby’s object oriented
design. Amrita (http://), an alternative to eRuby, is a HTML/XHTML tag
attribute-based markup syntax making for excellent speration of content and
logic. For accelerated execution, mod_ruby (http://www.modruby.net/), the
Ruby Apache module, embeds the ruby interpreter directly into Apache, much
like mod_perl, and is quite stable, now at version 1.0.2. There are also
complete frameworks like CGIKit and ILE (http://virtualschool.edu/ile/) to
speed development. Web development with Ruby is very powerful solution and
is beginning to displace traditional Perl and PHP scripting. Expect to see
many new Ruby-based applications in the future!

dont forget english publication of ruby in a nutshell. :smiley:

···

On Sunday, January 5, 2003, at 02:40 PM, Mark Wilson wrote:

  1. The publication in early 2002 of The Ruby Way and Teach Yourself
    Ruby in 21 Days. Any others? Also any interesting books in
    non-English?

An excellent milestone. Congratulations, Hal.

Gavin

···

On Monday, January 6, 2003, 5:49:05 PM, Hal wrote:

FWIW, The Ruby Way was translated into Japanese in late 2002. I’ve been
meaning to announce that for whoever’s interested. Guess I’ll do it formally
soon.

Thank you for the kind words. Please Wikify it, unless Phil Tomson has
done so already. I’ll figure out how to use wiki in order to make
further contributions.

Regards,

Mark

···

On Monday, January 6, 2003, at 12:01 PM, Lyle Johnson wrote:

Mark Wilson wrote:

The following is my contribution to this project. I think I have
exhausted my capacity to add additional content without doing further
research. I will happily continue to help however I can and can also
contribute to editing and to adding links where needed. Feel free to
edit, rearrange, use, not use, etc.

This looks great so far. Like some others on the list, I’d like to
help out if needed. I just checked the Ruby Garden and it doesn’t look
like anyone has Wikified this yet – should I go ahead and do that or
have you guys already got a working document in place somewhere else?

– Lyle

Hi,

···

In message “Re: Forward: Drafting a “The Year in Scripting Languages”” on 03/01/07, Lyle Johnson lyle@users.sourceforge.net writes:

I just checked the Ruby Garden and it doesn’t look like
anyone has Wikified this yet – should I go ahead and do that or have
you guys already got a working document in place somewhere else?

Just go ahead, please. It’s embarrassing that I’m ignorant about
Wiki operations.

						matz.

How about The Ruby Developers’ Guide?

Brennan Leathers wrote:

···

dont forget english publication of ruby in a nutshell. :smiley:

On Sunday, January 5, 2003, at 02:40 PM, Mark Wilson wrote:

  1. The publication in early 2002 of The Ruby Way and Teach Yourself
    Ruby in 21 Days. Any others? Also any interesting books in
    non-English?