pl/Ruby, deprecating plPython and Core - Mailing list pgsql-hackers

From Joshua D. Drake
Subject pl/Ruby, deprecating plPython and Core
Date
Msg-id 4300D145.90307@commandprompt.com
Whole thread Raw
Responses Re: pl/Ruby, deprecating plPython and Core  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pl/Ruby, deprecating plPython and Core  (Tino Wildenhain <tino@wildenhain.de>)
Re: pl/Ruby, deprecating plPython and Core  (Hannu Krosing <hannu@skype.net>)
Re: pl/Ruby, deprecating plPython and Core  (Thomas Hallgren <thhal@mailblocks.com>)
Re: pl/Ruby, deprecating plPython and Core  (Dave Cramer <pg@fastcrypt.com>)
List pgsql-hackers
Hello,

I have negotiated with the author of pl/Ruby to release plRuby under the 
PostgreSQL license. The reason I did this is the following:

1. I felt we needed a truly OO language in core.
2. plPython isn't really moving forward and has the whole 
trusted/untrusted issue.

Now anyone who knows me, knows that I love Python which means this is 
not a language argument as much as a functionality argument.

Ruby for good or bad is gaining a large following and has become a very 
active language in a short period of time. It can also be trusted and 
untrusted.

I believe that unless plPython can either be fixed or is going to 
continue to move forward as a pl language that we should consider 
deprecating it and even removing it in 8.2 or 8.3.

As far as a PL language plruby seems to have some really good stuff. 
Here is the docs:

http://moulon.inra.fr/ruby/plruby.html

What does everybody think?

Sincerely,

Joshua D. Drake






-- 
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Upcoming back-branch releases
Next
From: Tom Lane
Date:
Subject: Re: pl/Ruby, deprecating plPython and Core