Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl Monk, Perl Meditation
 
PerlMonks  

Re: Arguments needed for comparision between Perl, ASP and Java

by Art_XIV (Hermit)
on Nov 10, 2003 at 16:51 UTC ( #305913=note: print w/replies, xml ) Need Help??


in reply to Arguments needed for comparision between Perl, ASP and Java

Having worked w/Perl, Java/JSP, and ASP/ASP.NET, I can sincerely state the following - Java and/or ASP are better because Sun/IBM/Microsoft have multi-million dollar marketing budgets that say they're better.

It's not unusual for developers to be passionate about languages and prejudiced in favor of or against various languages. I guess this is a side-effect of so many developers being INTJs. ;)

Bold generalizations follow, but I try to make them with an open mind and sense of fairness:

  • A Perl app can be written much faster than any comparable Java/.NET app when written by developers of comparable skill.
  • A Perl app will tend to run a little slower than a comparable Java (1.3 +)/.NET app when written by highly skilled developers.
  • Its anybody's guess how the performance of apps will compare when written by relatively low-skilled developers. Java and .NET have many performance traps for novice/indifferent developers. If I had a dollar for all the string-concatenation in loop problems, inappropriate use of reflection problems, poor use of the database problems, etc... that I've seen w/ Java and .NET, I'd have at least a mortgage payment. And I'm only counting code written by 'professional' developers.
  • Code quality has very little difference. Perl may even have an edge in many cases since it's so easy to get Perl to do what you want it to do w/o funky work-arounds or extra reams of code.
  • Maintainability is harder to assess. It can be hard for a team of developers to work with Perl, but its hard for a team to work in any language. Communication and documentation are what counts, here. Perl can be a 'Write-Once, Run-Only' language when it's written to be such, but it can be very understandable when written to be such.

The performance, quality, and maintainablity of any application is going to spring much more from the skill, talent, dedication and self-discipline of the developer(s) and the amount of quality design time that is put in than it will from the language/platform choice. Developers can produce something beautiful with Perl, Java, or .NET. They can also produce slow-running, unmaintainable crap with any of the three.

When someone asks me 'Why do you use Perl? Java or ASP is much better.', I ask them 'How did you come to that conclusion? Have you used both Perl and <language/platform x>?'

80 percent of the time the response is "No", possibly with some baloney about how CGI has to spawn a new process or "Perl is too hard to understand" or "Perl looks like line noise" or some hooey along the same lines.

Have no doubt that I like Perl, and I like it alot. Putting more tangible qualities aside, writing Perl is a lot more fun than writing Java or .NET. And fun matters when you spend all day coding. Perl values my time more. Perl doesn't make me sweat over the mundane. Perl is easy to learn yet difficult to master. Perl helps make the journey as enjoyable as the destination.

Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"
  • Comment on Re: Arguments needed for comparision between Perl, ASP and Java

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://305913]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (5)
As of 2021-01-18 09:46 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Notices?