Re: A response?

The technical differences between Python and Perl aren't very relevant to this discussion (where the use case is extending Vim via Perl), and you will not do any favours to the Perl community by taking a (metaphorical) dump on Python.

Perhaps you can simply point out that well known projects like PostgreSQL, Apache and Nginx all support extension via Perl, and that you and others would like to have the same facility with Vim.

Comment on Re: A response?

Replies are listed 'Best First'.
Re^2: A response? by locked_user sundialsvc4 (Abbot) on Mar 13, 2014 at 01:47 UTC
Another way to look at it is ... “do we really have A Problem here?” Most of us, I daresay, actually are well-versed in all of these languages. Chances are, many of us switch without pause between several of them every day. So, if Vim currently supports Python but not Perl, “hey, it’s really no big deal.” As long as we can write macros in the thing, one way or the other, “it’s all good.™” The digital computer doesn’t have to be versatile, since we are. So-o-o... is there, in fact, a business justification for Perl support in Vim (on all of the various environments that Vim is expected to simultaneously support)? ROI = Return On Investment? If the answer is “yes,” then I guess we need a Volunteer. If the pragmatic answer is “no,” that’s actually okay, too. Either way, it says absolutely nothing for/against Perl, “and ditto Python.” At the end of the day, all of them are just tools within our toolbox, and I think it’s kinda silly for a hammer to be arguing with a screwdriver. (I will very-diplomatically leave it as An Exercise To The Reader™ which one is which ...) `;-)`

Replies are listed 'Best First'.

Re^2: A response?
by locked_user sundialsvc4 (Abbot) on Mar 13, 2014 at 01:47 UTC

Another way to look at it is ... “do we really have A Problem here?” Most of us, I daresay, actually are well-versed in all of these languages. Chances are, many of us switch without pause between several of them every day.

So, if Vim currently supports Python but not Perl, “hey, it’s really no big deal.” As long as we can write macros in the thing, one way or the other, “it’s all good.™” The digital computer doesn’t have to be versatile, since we are.

So-o-o... is there, in fact, a business justification for Perl support in Vim (on all of the various environments that Vim is expected to simultaneously support)? ROI = Return On Investment? If the answer is “yes,” then I guess we need a Volunteer. If the pragmatic answer is “no,” that’s actually okay, too. Either way, it says absolutely nothing for/against Perl, “and ditto Python.” At the end of the day, all of them are just tools within our toolbox, and I think it’s kinda silly for a hammer to be arguing with a screwdriver. (I will very-diplomatically leave it as An Exercise To The Reader™ which one is which ...) ;-)