J2EE vs. .NET
Steve Anglin: Has Java passed its prime?
We watched the season premiere of Alias last nite. We had to tape it since we were invited to Vicki's brother for dinner..NET is a force to be reckon with. Once the M$ stream-roller marketing machine is in motion, there's no stopping it.
The marketing message never changes. It is just repeated over and over and over. The theory being that if you repeat it often enough, people will simply believe it. Guess what? It works. The press/media will bark at first, but ultimately fall by the sideline.
In the IT world, decisions are made by people that truly want to believe the hype. In the end it is never about technologies that are available today, but about what Microsoft claims they can provide tomorrow. Whether they can actually deliver becomes a moot point.
The whole J2EE vs. .NET debate has nothing to with bias toward or against Microsoft or Sun. Microsoft, like Apple and countless others, has a horrible track record when it comes to delivering new technologies in a timely fashion. Decision makers should realize that basing the future of a company on forthcoming technology implementations is foolish.
I don't blame Microsoft. I applaud them.
Unfortunately, we missed the last 5 minutes. The preceding football game ran overtime. Another reason why I can't stand football.I was a little disappointed with the whole show. I was expecting it to start with a bang, and it didn't.
Anthony: Perl v. Java My Ass.
I've always said that a smart programmer should use the language that is the best suited for the task at hand. There is no one language that does it all. Java's pretty close though.
IBM releases WebSphere Studio 5.0.
Red Hat rolls out Linux 8.0.
Gert Van Ham's released version 0.4 of his JCE taglib.
Sun announces new J2ME APIs and J2EE improvements.