Re: [proposal] Libary changes

[Tim Caswell <tim@...>]

Sebastien, there is no need to take offense.  It's hard to gauge what
you know based solely email conversations. (Heck it's even hard after
having a one hour job interview in person).

I've found in open source communities, it's much more effective to
explore the idea a little on your own, have a proof-of-concept
implemented and then submit a proposal with clear pros and cons of the
idea.  And above all, don't take offense when someone doesn't
understand.  They are not you.

FWIW, I agree that lua dumps way too much in the global space.  It's a
bad practice and usually when I bring it up to people, the response
is. "Hmm, I haven't thought about, you're right we probably shouldn't
do that"

As far as my experiment, here is what I've got so far:
https://github.com/creationix/luvit/blob/master/lib/luvit.lua#L1-12

It breaks a lot of third-party code, but to me it's worth it to have a
cleaner global.  That's my personal taste, but I'm putting my "code
where my mouth is".

We're all going to be in this field for many years to come.  Let's
remember that there are real people on all sides of an email thread.

-Tim Caswell


On Tue, Oct 11, 2011 at 2:21 AM, Sebastien Lai <237482@googlemail.com> wrote:
> On Tue, Oct 11, 2011 at 9:55 AM, Michal Kottman <k0mpjut0r@gmail.com> wrote:
>> The concept that confuses you is called a "scope"
> I'm pretty sure - no, i *KNOW* that I'm perfectly aware of the logic
> of scopes in programming languages, not just in Lua
>
> But this thread is not about me, it's about Lua. And I refuse to
> justify myself here any further.
> This attitude is plain and simply rude and unnecessary.
>
> This thread is about a proposal. There hasn't been a single line of
> realworld code written to support this proposal, no Lua fork has been
> created yet, no documentation has been written yet, no community
> created, no money made. Keep that in mind. It's a proposal. Nothing
> more.
>
> This thread is very clearly going nowhere. And I start to regret that
> I shared my Idea on lua-l in the first place.
>
>