The issue here is not the underlying architecture. I have seen so-called "Enterprise"
solutions which are based on the most flakey of ideas, but are sold with a $150k+
pricetag. Why? Because of the integraiton. Because of the support.
I a large company, you cannot *afford* to have the ubergeek cureall solution. What if
the guy gets hit by a bus? What if he goes to another company? You can't afford that
kind of situation. What do you do in that case? Make the system easy enough to use
and understand, that you can have 5-ubergeek types at the company. Sure the system
isn't a screamer, but atleast it doesn't take a genious to understand.
Also, systems like EmbPerl, HTML::Mason and Axkit/Cocoon work wonders for shops with
under 10 developers. What happens when you have 20 programmers, 15 workflow people,
45 content creators, 10 photographers, 20 HTML designers / producers, 30
merchandisers, 30 marketers and a host of misc. consultant copywriters? How do you
coordinate everything? A large online retailer, news site, portal, you name it...has
a *lot* of employees. *That* is what an Enterprise is...and anyone who says you can
"get by" with an HTML::Mason is diluted.
Now, I use HTML::Mason, and I love it...for my personal website. I'm sure many
organizations can get by with it. But, thats not what I'm talking about, and thats
where Java is winning. What happens when all those programmers working on Java
solutions decide to build something at home? They'll use Java.
If you remember, Apple tried to appeal to schools and home users, and M$ focused on
business. Who has all the marketshare now?
The answer isn't in the hobbiest or in the small sites. For longevity and mindshare,
you must go into the big businesses.
My company is a Perl shop, through and through. We would rather go to Perl, but the
problem is that theres *nothing* out there. Please prove me wrong.
--man
Michael A. Nachbaur
-----Original Message-----
From: Thomas J. Mather [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 05, 2000 10:25 AM
To: [EMAIL PROTECTED]
Subject: Re: mod_perl advocacy project resurrection
On Tue, 5 Dec 2000, Michael Nachbaur wrote:
> I don't know what I'm getting at here, but I see that Perl is half a
> step behind Java in many ways, except for the performance issues
> (which perl is leagues ahead). For my company, we're probably going
> Java, but it sorta makes sense for us (we need an enterprise solution
> now...not when the Perl community gets around to it).
How exactly does Java provide a better "enterprise solution" than
Perl? And how can the Perl community better provide an "enterprise
solution"?
It is true that Java code is generally more cleaner and easier to maintain
than Perl code, but this is because Perl allows you to write bad code,
while Java enforces typing and OO design. A good Perl coder should
be able to write code that is clean and easy to maintain by following
coding guidelines, and by using OO modules and 'use strict'.
I guess what I'm getting at is that I hear a lot of marketing hype about
Java being a better "enterprise solution", but I'm curious as to what are
the purely technical reasons for using Java over Perl. What exactly can
you do in Java that you can't do as easily in Perl?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
