Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of alexchorny@gmail.com
 designates 209.85.221.109 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=WRT1A1OoTlctDtxsFawEQ0R8F41aK1M5Wi3t90BBZ7hW0AakDVFcWzFYWMBG8XcB0g
         ujcbaexOY7tOSA45EdJOmBZtppYKLpdcF1UUFXTkwlDPZBBoE80Gg8TUcdz0owl3bO0R
         uzpvrGrTOd4AV26+IO/T3tdXHlQKAoKRJrols=
MIME-Version: 1.0
In-Reply-To: <F9933873B8C841B3A630EC0E27856E6A@teddy>
References: <20090323130731.GA21057@apartia.fr>
	 <49C7C78C.5030504@norchemlab.com>
	 <F9933873B8C841B3A630EC0E27856E6A@teddy>
Date: Mon, 23 Mar 2009 22:06:15 +0200
Message-ID: <2f1541220903231306g2a7e8e1fu90c2ef682c9fa54f@mail.gmail.com>
Subject: Re: decline and fall of modperl?
From: Alexandr Ciornii <alexchorny@gmail.com>
To: =?ISO-8859-1?Q?Octavian_R=E2snita?= <orasnita@gmail.com>
Cc: modperl <modperl@perl.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi.

It possible to encrypt perl sources with same safety as with PHP -
with possibility of source decryption. But Perl developers are in
general more advanced than PHP developers so they know how to decrypt
it, in contrast to PHP developers that do not know that encrypted PHP
sources can easily be decrypted. There are also some bytecode
compilers for Perl (alpha stage).

2009/3/23 Octavian R=E2snita <orasnita@gmail.com>:

> PHP, C#, Java are much more prefered, because the programs created with t=
hem
> can hide the source code much better, while this is not possible with Per=
l.
> This is a big reason why the software companies that create custom progra=
ms
> for their clients prefer to use those languages and not perl. Not because
> perl is bad.

--=20
Alexandr Ciornii, http://chorny.net