Microsoft should have used Java or .NET in the least

Miscellaneous Topics
#1

I thought this comment was VERY interesting although not entirely sure if it’s correct. Maybe someone here knows more?

[quote]I predicted in /. forum that XBox will be very unstable, not because it is designed by MS but because it is nightmare for debugging. You have to make 3 threads application (not 4, not 2) and sync all objects they share. Combine it with complicated interactions of objects in any game, which makes creation of auto-test scripts impossible and default gaming language, C++, which is very uneasy to debug for Multiple threads (compared to say, Java) and they hardly could do any better than this. Cell is designed in much better way, multiple threads (SPUs) are used by low level liberaries (well debugged) but main gaming/engine app. is still single-threadded and therefore easy to debug and stable.
[/quote]
For a system as powerful as the X-Box I would think they could spare a few cycles to get a huge increase in usability, debugging and memory management along with SAFETY.

#2

100% logcial and 100% not goign to happen.

It would defeat MSFT’s primary purpsoe with X-Box, which is to promote their APIs and thus control development.

#3

… and to RULE THE WORLD!! MUHAHAHAHAHHAHAHAH!!!

On the other hand, I have heard that the X-box 360 isn’t nearly as bad to develop for as some think. You don’t need to use multiple threads for one and two debuging them isn’t nearly as hard as the /. poster suggested it is. Several of the top games being developed for the 360 are using multiple threads. I think this is more about people fearing change. Multi-threaded programming, especially in games, is not something people are used to. Those embracing it appear to be doing fine.