When you spend pretty much all your work time coding, adding in features to a language doesn't seem that onerous to me. If you are a casual coder, I could see C# being a bit overwhelming.
On Jan 9, 5:35 am, Casper Bang <[email protected]> wrote: > On Jan 9, 1:02 pm, John Wright <[email protected]> wrote: > > > I second this - keeping up with the pace of change of C# and .NET 2.0, > > 3.0, 3..5 etc is a fulltime job! > > And in Java its a full time job to keep up with all the libraries and > frameworks, largely because the out-of-the-box experience is so lousy > and innovation HAS to take place in external libraries. So I guess I > find that argument rather weak, although I understand the HR concerns. > Example: A C# assembly has encapsulated the versioning aspect from day > one, something that's handled in a myriad of ways in Java, either by > OSGi, NetBeans Module System, JSR-277, Jigsaw... + a very long list of > classloader hacks. > > /Casper --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
