> The .Net crowd seemed on average less clued up that the
> Java crowds I had dealt with and many produced messy, hacky code.
My experience is that the bar of entry is lower with .NET - regardless
of its higher language feature matrix. It's just harder being a Java
developer, where few things are handed to you on a silver platter (you
need much more external knowledge of idioms, patterns and frameworks).
OTOH those are HR issues, a developer that cares can go far and write
professional code regardless of the language.
On average I think the Java crowd is probably smarter, but also more
close-minded ("I don't need no stinkin' properties, what's wrong with
rolling your own observer pattern using PropertyChangeListener?").
The .NET crowd is more pragmatic in trusting that certain choices have
been made by people smarter than themselves, even if that may not
always be the case.
For a long time I was hoping Java would steal back from C# (only
happened with annotations AFAIK), gain some pragmatism (decimal
literal, properties...) and generally start pushing the art forward
again. However, now I no longer think that will happen. Java is far
from dead of course, but I question how it will remain relevant to new
and upcoming developers confronting ever-escalating application
complexity. That's just my view of course, but arguably it's the same
realization driving adoption of a certain scalable JVM language.
--
You received this message because you are subscribed to the Google Groups "The
Java Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
