Re: pl/Ruby, deprecating plPython and Core

On 15-Aug-05, at 1:30 PM, Joshua D. Drake wrote:

> 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.
Why ? Are you truly going to write huge OO functions inside the db ?
If not why do you need OO ?

This looks to me to be just another syntax, what can you do in plruby
that you can't do in plpgsql, or plsh, or pltcl, or pl<name> ?

> 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/
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>
>