> > I am dealing with. There is nothing stopping individuals writing well > architected code in .Net but culturally unfortunately a lot of .Net > developers don't care as much about clean code as the typical Java > developers do. >
Traditionally you get fewer readily-available parts served in Java, so it's true that the .NET crowd doesn't cultivate quite the same... ingenuity. I.e. what seasoned Java developer hasn't rolled their own ORM, remoting and Web framework?! I happen to be in full agreement with you, that VB is just not worth the job. VB(.NET) exists as a pseudo-link to the old established non-programmer VB6, but it remains a subset to C# (except for having XML literals). There's no reason to get into VB.NET, it's first and foremost in C# progress happen. It is obviously beneficial to know both C# and Java, you can learn stuff from both. If some uptight Java-only shop considers other language skills harmful, then you probably won't find particular stimulating input there anyways. Unfortunately it's been seen before and while not as bad as in the past, you can still see demonization of alternatives (JavaZone) rather than actual objective comparisons. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/lPXzCrL08oYJ. 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.
