Long weekend...
By CosmicConservativeSo, blogging was very slow this weekend. The reason is because I have been trying to get up to speed with programming in .NET for a project I am working on. In my programming days I used to be a C/C++ programmer, but four years ago I shifted to java programming in a J2EE environment. I've pretty much avoided Microsoft's .NET environment except for a short period two years ago where I worked on a few .NET projects as a project coach. But virtually no coding was involved.
So this weekend I have been working through the installation, configuration and initial "Hello World" type of programs in the .NET environment.
Now, I'm not really Microsoftphobic, but I am certainly no fan of theirs either. This experience is one example of why. I won't go into all the licensing and proprietary software issues I've encountered, I'll just say that for the average person programming in java in a J2EE environment will cost hundreds, even thousands of dollars less than a comparable Microsoft .NET setup. This is because most of the J2EE architectural components can be had from Open Source sources like Jakarta.
For example, in .NET if you want to run active server pages (".asp" development) it appears you need to run Microsoft's Internet Information Services (IIS) platform. Well, that is only available if you purchase Windows XP Professional, which is roughly $100 to $150 more than Windows XP Home. The comparable J2EE product is called the "Apache Web Server" coupled with an application server like "Tomcat." These are free for downloading and run on pretty much every platform.
Likewise, if you need a database in the J2EE world you normally use mySQL, which is again, free. In Microsoft's world you probably can use mySQL, but your world will be much easier if you simply use Microsoft's SQL Server Enterprise, like all good little Microsoft Developers. Of course that means you need to install Microsoft SQL Server, and again, that ain't free.
What I ended up doing was upgrading to Windows XP Pro, and upgrading to the latest version of Microsoft Visual Studio .NET 2003. I'm not sure what my total investment is, but it is probably close to $1,000 just to be able to develop and run code that can be deployed to an enterprise .NET environment. Luckily I had some of this already set up from my previous encounter with .NET so it wasn't necessary to purchase everything from scratch. But still, I was very much less than thrilled to learn that my old Windows 2000 OS supported IIS, but the Windows XP Home (which was billed as an "upgrade" to Windows 2000) did not and I had to shell out an additional $150 to upgrade to Windows XP Pro just to get the same capability my old Windows 2000 already supported.
But, hey, Bill needs the money, right?
Anyway, I'm going to be pretty busy for the next few (several?) weeks working on this project. Blogging could be light for a while.
Comments (0)
No comments on this post.