Re: Re: Re: perl2exe - no more secrets

Enterprise development? It sounds more like you're talking about packaged commercial applications. Enterprise development usually means something built in-house that is specific to a business. These days it often means putting the company's business on the web, which would not involve a compiler.

I agree that the inability to effectively compile Perl works against it being used to build packaged commercial software, but that's a fairly unusual thing to choose Perl for. That realm seems pretty well locked up by C++. Perl is more at home on the server side, where this sort of thing is not an issue.

Comment on Re: Re: Re: perl2exe - no more secrets

Replies are listed 'Best First'.
Re: Re: Re: Re: perl2exe - no more secrets by Anonymous Monk on Feb 26, 2003 at 12:38 UTC
Sorry, wrong buzzword. You got my point though :) As for using perl for packaged commercial software, I mostly agree with your point. Personally I wouldn't use perl for such a project but there are those who definately would like to. I think it also applies to the server-side. Sadly, not every company wants to give the source out to every product they sell. This leads them to other languages. Is this good or bad? Hard to say, but people shouldn't be surprised when some companies don't consider perl and option because of it.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: perl2exe - no more secrets
by Anonymous Monk on Feb 26, 2003 at 12:38 UTC

Sorry, wrong buzzword. You got my point though :)

As for using perl for packaged commercial software, I mostly agree with your point. Personally I wouldn't use perl for such a project but there are those who definately would like to. I think it also applies to the server-side. Sadly, not every company wants to give the source out to every product they sell. This leads them to other languages. Is this good or bad? Hard to say, but people shouldn't be surprised when some companies don't consider perl and option because of it.

[reply]