Java API and Microsoft's .NET API: a Comparison
319
Nerval's Lobster writes "Previously, developer Jeff Cogswell focused on the respective performances of C# and Java. Now he's looking at yet another aspect of the languages: the runtime libraries—what exactly the libraries are, how they are called, and what features the languages provide for calling into them. Examining the official Java API (now owned by Oracle) and the official .NET API owned by Microsoft, he finds both pretty complete and pretty much a 'tie' with regard to ease-of-use and functionality, especially since Java version 7 release 6 allows for automatic resource management. Read on and see if you agree."
Re:first (Score:2, Funny)
Damn my Java client!
Re:I don't want to be "that guy", however (Score:5, Funny)
In closing, C# .NET > Java.
Please address .NET hate-responses to /dev/null
Your windows environment has /dev/null?
How cool is that?
Re:I don't want to be "that guy", however (Score:5, Funny)
Re:I hate them both (Score:3, Funny)
Re:I hate them both (Score:1, Funny)
I guess it was easy in the old days when no one gave a shit if your software actually did anything. Unfortunately for the real world, you don't just get to target 15 or 20 experts anymore. There are now BILLIONS of users.
The scale probably hasn't sunk through the grey yet, but don't worry, you'll die someday and not have to worry about it.
Re:I don't want to be "that guy", however (Score:4, Funny)
In .NET, everything is an object.
Unless it isn't, of course.