Leon Rosenberg wrote:
As I wrote in the answer to dave: c is not c++. The main problem of c++ was
actually, that they kept all the c-shit (yes powerful, but absolutely
unmaintenable stuff ) in the language.
I don't know where you're getting that "unmaintainable" bit from.
A printer company I worked at had an approx. 1 million line codebase in
C and I was productive in under a week; that doesn't sound
unmaintainable to me.
If you had a bad experience with C I'm sorry, but I really don't
understand some of the assumptions you're making: my experiences have
been with well-coded and documented systems, some quite large.
I can make ANYTHING un-maintainable. Similiarly, I can make ANYTHING
maintainable.
Ok... What do you guess, what is the number of use cases for an average
"pissy" web-portal?
What's the number of usecases for a bloody spreasheet?! Each function is
a usecase. Combinations of functions might be individual usecases.
Macros. GUI. Reporting. Spreasheets are far more complicated than a
portal, and are, in fact, more complicated than most websites.
I don't know it either, but there were some studies back in the 96, 97 that
an average java developer produces 10-15% more locs a day, then an average c
developer. And by "produces" I mean, tested, working and documented code. I
think to remember that it was
about 45 loc a day for a c developer, and 55 for a java developer.
And the numbers for Lisp vs. Java productivity are on the order of 2-10x
of a Java developer.
I don't judge productivity on LOC, though, since I can accomplish a lot
more in Lisp with the same number of lines of code in Java. Heck, I
could produce many more times the LOC in assembly, tested, documented,
etc. than I could in Java :D
As a technical lead, if you show me ten classes each
containing only 20 lines of code, then you'd better be
prepared to explain yourself.
There are as many opinions as there are architects/leads/senior developers.
Next time you have someone with 10x20 send him to me, we are always looking
for good people.
I'll do that--10x20 reeks of over-objectification. Heck, I tend to think
a method is too long if it has over 40-50 LOC. Anything 10x20 probably
shouldn't have been written in Java to begin with.
I think Java is acceptable for Pretty Large Projects, with Large Numbers
of developers, especially if they're Geographically Distant. I'm
struggling to come up with a 10x20 program that would benefit from being
written in Java that wouldn't suck, and I _like_ many parts of OO!
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
