News for hackers. Stuff that matters.
Re:.NET Culture Shock by borisk on Friday June 25, 2010 @06:34PM (#1462410)
Microsoft has kept introducing major features in .NET every few years - generics, WCF, WWF, WPF, LINQ, EF, PE, Rx... So most of the millions .NET developers spent most of their learning time on those. On the other hand since 1.2 the only major and widely used new feature in Java is generics. And the focus in the community has been on patterns like DI, AOP, DDD, TDD ...

IMHO .NET still has one huge advantage - developing UIs for enterprise apps. Very easy to learn drag'n'drop win/web forms + multiple control vendors. Real component oriented programming.

Re:.NET Culture Shock by motters on Friday June 25, 2010 @06:38PM (#1462422)
This year by year increase in features - what I refer to as the "TV remote effect" - is of concern. Really they ought to concentrate upon consolidating and removing unnecessary features from the language.
Re:.NET Culture Shock by SamReidHughes on Friday June 25, 2010 @06:59PM (#1462482)
This year by year increase in features - what I refer to as the "better than Java effect" - is not of concern. They're not going to remove features from the language, because that would break existing code for no reason, and that would be insane. The only reason to remove a feature is if it can cause damage. Maybe Scheme should get rid of call-with-current-continuation, but I can't think of any features C# needs to get rid of. Can you?
Re:.NET Culture Shock by InclinedPlane on Saturday June 26, 2010 @01:00AM (#1463144)
.Net frameworks are not identical to the JVM. The general principle of the JVM is that it remains binary compatible across all versions (this limitation forced severe constraints onto the implementation of java generics, for example). In contrast there are multiple versions of the .Net runtime (CLR) that are not compatible. MS often makes breaking changes across major versions of the CLR.
Re:.NET Culture Shock by xtho on Saturday June 26, 2010 @03:09AM (#1463297)
AFAIK JVM byte code isn't guaranteed to be backwards compatible. They also introduced new byte codes that didn't exist in earlier versions. In that sense, there also are different versions of the JVM.
Re:.NET Culture Shock by jules on Friday June 25, 2010 @06:48PM (#1462450)
Removing features is impossible. The best you can do is starting over once in a while.
Re:.NET Culture Shock by contextfree on Friday June 25, 2010 @07:19PM (#1462552)
You can sometimes get away with removing features under the guise of a "compact" version for a new platform, e.g. OSX -> iOS, WPF -> Silverlight
Re:.NET Culture Shock by borisk on Friday June 25, 2010 @07:03PM (#1462496)
Some ppl in Microsoft see F# as exactly this fresh start.
Re:.NET Culture Shock by xtho on Saturday June 26, 2010 @03:10AM (#1463301)
IIRC Java has removed features in the past by marking them as deprecated for several releases and then removing them.
Re:.NET Culture Shock by angstrom on Friday June 25, 2010 @08:38PM (#1462721)
I think the language has evolved well, but the framework certainly has some useless cruft. Luckily that can be ignored.