[quote]Ive been on some other forums (Like ehm Xith) and I hear all this talk about how Java3d is dead, how it stopped evolving, how sun stopped its support.
[/quote]
Sun tried to do to 3D what they did to Swing. Which was a big mistake. The 3D performance and hardware at the time lacked to make up for the bad 3D pipeline in Java3D. So it could run anywhere, but not very well.
Finally they placed the developer to high up over the Java3D API preventing them from being able to do a lot of 3D applications people come to think of when they think “3D”. For example: 3D video games, 3D drafting and design, and 3D visualization. All these need a different rendering solution, and no one solution can be perfect in all cases.
Bias alert: I hated Java3D. It’s like Visual Basic for 3D programmers. We finally have access to OpenGL bindings, and this going to be the future of 3D on the Java platform.
[quote]Another outrageous comment I hear alot these days, is that Java itself is dead, Killed by the total superior .NET ?! :
:
[/quote]
The problem with .NET is that it’s not a technology. It’s a “brand name” for most of Microsoft’s products. For example (Access .NET, SQL .NET, Fortran .NET, C# .NET, Word .NET). When you compare Java (a technology) with the worlds largest software company’s line of products the scale is going to tip to one side with a crash.
When thinking in terms of Java you have to remember that Sun has always been an “out of the box” solution provider. Releasing products that no one else has, and it’s a smaller company. How many companies the size of Sun have this many developers using their products? Maybe Borland or a couple of others, but you could most likely count them on one hand. Now, stop and see how scared Microsoft is, how much people talk about .NET vs Java, and you’ll begin to see who is the trend setter, and the follower.
It doesn’t matter if .NET becomes the next “big” thing, because Sun is working on the next new thing. Try to remember how many years Microsoft developers were forced to write applications in C++ using the old Win32 API. Microsoft just can’t change quickly, and the amount of increased features in Java 1.0 to 1.5 beats out most work done by Microsoft in the last 8 years. Microsoft’s .NET isn’t new it’s just them catching up to what the industry is expecting as solutions in development. In order for .NET to be successful it has to be amazing. Else, people will point the finger at Microsoft and say “you idiots you did it again”. While people will always be talking about Sun saying “Wow, look what’s coming now”.
So I say to Microsoft. Bring it on! Mother f###er. ;D