in reply to Re: Re: J2EE is too complicated - why not Perl?
in thread J2EE is too complicated - why not Perl?

One thing missing in this discussion is that if I write a commercial application in Perl, how do I sell it without exposing the code?

I was asked about it in my company when I wanted to write a tool. Even though we gave the tool to our customer, we did not sell it.

May be there is a way and I do not know it. I thought compiling it to native code is not supported yet.

Here is a cool idea:

Why not write Sun's pet store project in Perl and bench mark it?

  • Comment on Re: Re: Re: J2EE is too complicated - why not Perl?

Replies are listed 'Best First'.
Re: Re: Re: Re: J2EE is too complicated - why not Perl?
by petesmiley (Friar) on Dec 10, 2003 at 17:37 UTC
    I know this is an entirely different discussion, but...
    why would you need to hide the code?

    If I want to look at the guts of a java program (which isn't native to anything but a JVM) I can just decompile it.

    Just an opinion but, to me IP law is what protects code ownership, not hokey compilation schemes. If someone wants to steal your program, they're gonna steal your program.

    If the program is legitimately yours, then good customers will pay for it. I've seen some ginormous products, written in Perl, come in the door where I work, and it never kept the company from shelling out 6 or 7 digits for it. Granted, all of these products came with service contracts. But then again, I have this feeling high-end java based products come with service contracts as well.

    smiles

[reply]

In Section Meditations