The C# Programming Language for Java Developers
In the “Just come to the dark side” department:
Microsoft has an article that discusses the differences between C# and Java.
As always, it makes me look forward to JDK 1.5. I also really wish we had delegates, or groovy/ruby closures. They really change the way you work :)
MSDN “Java/.NET Dev Center” is up
In the “We want to play” department:
Microsoft has a new Resources for Java Developers site (which is where the above paper came from).
Ted says is all (after he gloats about being on the site :):
Please, by the way, if you’re a Java guy reading my weblog, don’t take this entry as an exhortation to convert. That’s not really the point of the site, though conspiracy theorists will of course dispute that; the point of the site is that there were damn few resources out there for the Java-backgrounded fledgling .NET programmer to consume, and Microsoft wanted to close that gap. Frankly, I think BEA and/or Sun and/or IBM should do the same: provide a “Resources for .NET Developers” page at the respective developer sites for each company, because programmers are going to be migrating back and forth between these two platforms for at least the rest of this decade. Neither one is going away.
June 9th, 2004 at 8:51 am
You are right. “Design Patterns” often seem to be workarounds for things that you can’t do nicely in your language. Closures are a cleaner way to do things in this case IMO, and having it as a first class operation is a subtle difference.
The same can be said for other patterns such as a Factory. If I am using AspectJ then I use mixins instead of having to have a factory class itself.