＋设为首页 ＋添加到收藏夹
part 1 of this series appeared in the august issue of java developers journal (vol. 8, issue 8), and part 2 appeared in the september issue (vol. 8, issue 9).
jdj: microsoft has received quite a lot of good press (or propaganda, however youd like to look at it) for their .net product, and there has even been discussion that it will be/is suitable for games development with good directx bindings. since java is only just out of the gate (in terms of commercial games development), do you see .net providing serious competition in this burgeoning market, or are there some (perhaps hidden?) advantages to java that might make the difference in this case?
jeff k: dont confuse .net the platform with clr the vm, or c# the language.
.net will not be suitable for games. its xml-based communications protocol is by definition slow and verbose, and thats before you get into the other architectural issues. i have no fear of .net becoming the default back-end technology for networked games - it was designed with business apps in mind, which need totally different properties.
as for c# and clr (which, as i understand it, are heavily based on msvm), there are a number of points. msvm has always supported directx through jdirect, but it hasnt taken off as a game platform. that they are continuing this support doesnt seem like anything new to me. c#/clr has none of the benefits of java (its not cross platform, being yadc (yet another dialect of c) its not likely to appreciably improve either productivity or code correctness.
about all it does is muddy the waters around java, which in my opinion is maybe all its supposed to do.
today we have cross-platform technologies emerging in java that provide all the benefits of directx without sacrificing portability, productivity, or code correctness. examples of this are the lwjgl open source library project, and the open source bindings for java to opengl (jogl), openal (joal), and ... 下一页