Re: The Lua Development Process: Why Closed?

[Bezobiuk Volodymyr <dedoogun@...>]

Hello Rob,

and if there were voting or so I will vote for the continuation of closed development process. Let me describe my point. As far as I know (from my own experience and also read and heard from others) maintenance of piece of code is quite a time-consuming task. If it's fairly big enough i mean _really time consuming_. Either you lose the control over things and then the code loses his clear insight shape (leading to small but ugly and annoting inconsistencies), or you spend more time checking and reviewing patches etc, instead of developing the masterpiece. Yay, I understand the Lua parents, really. It's like giving your child to some 'really careful babysitters', this is not ok. I personally like the spirit of Lua as being much less commercial than, f.e. Ruby world. Ruby are getiing bloated by 'features' because of this, and it's not so stable, etc.

So it would be better to continue as is, in my opinion...

On Mon, Nov 12, 2012 at 11:18 PM, Rob Hoelz <rob@hoelz.ro> wrote:

Hey everyone,

This is a question I've been thinking about for some time; although my
wording may come off as a bit aggressive to some, please know that that
is not my intent.  This is an aspect of the Lua language and community
that I'm rather curious about; if this thread devolves into a sort of
flame war, please feel free to ignore it, or, if you have admin
privileges, close it.

So, the question is (if you couldn't tell from the title): why did the
authors of Lua decide to adopt a closed development process, and why
does this continue to this day?  By "closed development process", I
mean that unlike Perl, Python, Ruby, and other popular open source
languages, the canonical implementation's development is done by an
exclusive group, and the "work in progress" tree is not visible to the
public.  I find this very interesting, especially considering how
liberal Lua's license is.  I think it would be cool it other developers
would be able to directly contribute to Lua's development, but maybe
I haven't spent enough time thinking about this. =)

Thanks,
Rob