Someone a while a took the liberty of subscribing me to the "Java Developer's Journal". I'm not a Java developer, and honestly I hate the whole Java, Sun, and Oracle camp just as much or even more than anyone in that camp hates .NET and Microsoft. I must admit, this was a pretty good joke played on me by subscribing me to this magazine.
However, being the person that I am, I read alot of trade magazines, and usually over breakfast I'll read the magazines that I don't really care about. Yesterday I got the latest issue of the "Java Developer's Journal". What never ceases to surprise me in this magazine the amount of ignorance by the Java camp about .NET.
Today I read the editorial by Alan Williamson entitled "What's in a specification?". He talks about writing some methods for being able to remotely modify blogs at Blog-City using XML-RPC. Apparently the API for Blog-City is poorly documented and changes frequently. He then goes onto say how lucky he feels to be a Java developer since the documentation is so great and APIs are garanteed to be there. (Honestly this is a bunch of bull.) He then goes onto saying that this Blog-City API is like the Microsoft of APIs... I'm thinking to myself... this is complete BS now... the Win32 APIs are among the most widely used and least changing things out there (just new additions made, and occasionly every few versions a few APIs drops out). Then Alan goes onto to criticize C# and the .NET camp talking about methods not being there after a while. WHAT?!?!? This is total crap. I feel like yelling at this guy and reminding him that JAVA is the one that keeps deprecating APIs like crazy! (Here's a link to the "Java Developer's Journal" with this editorial I'm talking about. You need an online subscription if you're interested in reading it.)
Also, I'd like to remind him and all the other Java camp people out there who think that the Java Community Process (JCP) is the best thing since sliced bread that C# and the core of .NET are ECMA and ISO standards. That means 2 standards bodies stand behind it. Further that also means that any compiler or ".NET Framework" built must adhere to those specifications strictly. Unlike the JCP, these standards require for third-party standards bodies to approve additions or changes. In the JCP, ultimately it's down to Sun (JavaSoft) to make the decision. Here's the link for these specs if you're interested.
What sparked this blog is G. Andrew Duthie's post about the Computerworld article. Essentially what this Computerworld article is writing some misinformed crap, just like the Editor-In-Chief of "Java Developer's Journal" (ok, granted they will be VERY biased towards Java, but still, you expect them to state informed opinions).