in reply to Re: J2EE is too complicated - why not Perl?
in thread J2EE is too complicated - why not Perl?
oh sorry....
Ya know, these are the same people that decide that using the canned security in .NET and windoze is perfectly acceptable. But I guess some people have to learn the hard way. By the way, don't get the idea I've let this keep me from learning a little of it myself.
As for Perl in the "enterprise" (I never saw that part of Star Trek), I still agree with chromatics question. As for the definition, why isn't it simple? His was.
As for reading other peoples code and working in large groups, I would be willing to make a cheap bet. There is no project so big that you need so many programmers. I honestly believe many projects are over-engineered and the programmers under skilled.
I have never had the opportunity to work in large groups. However, that has never kept me working on large projects. Here are the reasons that I think (I could be wrong ;) there are very few differences between languages when it comes to big problems.
- A programming language will not make coders write good code, no matter how strict the language is.
- A programming language will not make coders write documentation, no matter how easy it is. And for those of you with experience you know how easy it is in Perl.
- A programming language will not make coders communicate with each other any better.
If you think about it, a language can only make these things worse by resisting the need of being intuitive. Skill, simplicity, documentation, and communication are all failing points of not only programming projects, but also businesses.
smiles
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Re: Re: J2EE is too complicated - why not Perl?
by podian (Scribe) on Dec 09, 2003 at 22:13 UTC | |
by petesmiley (Friar) on Dec 10, 2003 at 17:37 UTC |