Y'all are a bunch of wankers!

why is it good to go with one of the "big three" platforms ...

... ie Java, .NET, PHP, for an enterprise project?

The "you won't get fired" reason isn't one if you are a startup or whatever, because what counts is making the thing work and being continually able to do so.

The only two reasons that make any sense to me are:
- one having good and mature library support.
- being able to hire enough competent people down the line when you need to.
- the language/platform being mature enough.
Permalink $-- 
September 2nd, 2006 3:11pm
General availability of resources around those platforms is what makes them atractive.
Permalink Funny Bünny 
September 2nd, 2006 3:13pm
Yes. Those are THREE very good reasons.
Permalink Colm 
September 2nd, 2006 3:13pm
right. so I don't see the problem with perl then. You might have a problem if you need 100's of programmers I guess.
Permalink $-- 
September 2nd, 2006 3:21pm
Perl code maintenance is expensive and unwieldy, but yes, there have been tons of investment banks that have written millions of lines of production code in perl for precisely those reasons.
Permalink Colm 
September 2nd, 2006 3:22pm
That's a matter of opinion. No doubt there are plenty who have strong reservations about Java, PHP, .NET ... etc for various reasons. Personally I find it has more to to with the programmer.

I was wondering more about how it stacks up in the context of that recent debate.
Permalink $-- 
September 2nd, 2006 3:26pm
>That's a matter of opinion.

What is? Perl being a maintenance nightmare? I think it's more than that.

>No doubt there are plenty who have strong reservations
>about Java, PHP, .NET ... etc for various reasons.
>Personally I find it has more to to with the programmer.

Yeah. Wasn't that Joel's point?
Permalink Colm 
September 2nd, 2006 3:28pm
no. There are people who have shown themselves to be very good programmers who think it isn't, and others who think it is : therefore it os a matter of opinion.
Permalink $-- 
September 2nd, 2006 3:31pm
Such as?
Permalink Colm 
September 2nd, 2006 3:34pm
Perl works well for sys admin scripts - quick, dirty, and they FAST and efficient.  Biggest drawback is OO, therefore, you almost need Java/.net or C/C++ for a real project (or whatever, Ruby I guess).

The main drawback I see to Java is not being able to fully compile the source-code (like w/C/C++), and also I don't know how Java does it, but you want to be able to call/use some programs/code written in other languages as well, like C/C++.
Permalink LinuxOrBust 
September 2nd, 2006 3:34pm
I tend to see three separate families:
Shrinkwrap, scripting, and enterprise.
Permalink LinuxOrBust 
September 2nd, 2006 3:37pm
perl does OO fine. Biggest problem is if you really want to make some members genunely private - it's not easily done, although there are some modules I think. You rely on convention. Other than that, there is loads of OO code out there.

Colm, there is a shitload of good and well maintained code on CPAN. (There is a certain amount of bad code too, but so what. It can't be unmaintainable if a fair number of people have written modules which have been around for yonks, are in lots of real world systems, and that code has been maintained.)
Permalink $-- 
September 2nd, 2006 3:41pm
Well, with Perl people can just see your source code, and I don't see how you can protect it from being run without a product license key.  What about that?  yeah, OTW, it's just dandy.
Permalink LinuxOrBust 
September 2nd, 2006 3:45pm
there is PAR, which creates standalone executables. They are probably decodable if you are determined, but you don't have to distribute source.
Permalink $-- 
September 2nd, 2006 3:46pm
perl isn't an worse than PHP. surely it's not for desktop apps but for enterprise and scripting (where 'seeing the code' isn't an issue) ... that's two out of three. Not bad, considering only .NET even has a chance to do a hat trick.
Permalink victim of my own shyness 
September 2nd, 2006 5:37pm
>> Shrinkwrap, scripting, and enterprise. <<


There are significant differences in the level of quality expected with these.

Scripting: Just fix it -- you've got other things you need to be doing.

Enterprise: Fix it in a rush once it gets prioritized by the corporate bug committee that meets weekly.

Shrinkwrap: OMG!  We shipped a bug on write-once media to 130,000 customers!
Permalink xampl 
September 2nd, 2006 7:40pm

This topic is archived. No further replies will be accepted.

Other topics: September, 2006 Other topics: September, 2006 Recent topics Recent topics