Andrew, > I'm getting pretty board with these threads about the "death of > Java 3D", so I thought I'd make the current one longer :) > > What *technical* reasons are there for moving away from Java 3D?
I have two: dependence on a closed source API and lack of communication from the API developer. Communication is a vital part of Information Technology as is highlighted by this case even if it isn't strictly "technical". > With that list in mind, what other software *currently* fills the > gaps? > > And what does 'filling the gaps" mean (e.g. coding your > own shading algorithms?, waiting for the developers to debug > the promised feature in their software?). > > My opinion: Java 3D is the best mix of features, robustness, > good documentation, and online support/help *at the moment*. > So why change? How can you use a software library from a developer who has such poor communication that they won't even put to rest damaging rumours when they appear. It has been many months now with very little official word of Java3d's future. Java3d did not become bad - and indeed it is no worse than it was yesterday. What has changed is that many people's confidence in Sun as the developer of this API has been well and truly rattled and they are now scared to make new investments into technologies which use it. Now I don't think any of this spills across to Java - obviously Sun has a very good commercial case for continuing that, so I shall be using Java, open source 3D graphics but sadly no longer Java3D. Regards, Will. =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
