I'm curious how ask slashdot has become a free goole answers service... The person asking the question should really do some research first.
Some comments here:
1. Is it really the end of COM?
We (any.NET developer) hope so! But alas, I don't think the time has come yet.
2. Will ALL Windows programming be done with.NET?
Sure, you can do the hard core stuff in [Unsafe] C#/C++, leave the rest in.NET. What's wrong with that? Honestly you don't need to optimize some part of the application, like the start-up screens or the options dialogue.
3. DirectX is already available for.NET. Check DirectX 9 SDK, you can use it with C#, VB.NET, etc. There are sample projects everywhere.
4..NET Framework allows compiling down to native code, there is a.NET framework tool "ngen.exe" which generates a native image of your CLR assembly down to native code for YOUR machine - it will optimize for the particular processor. This is kept in the cache on the particular machine.
5. I personally think it's down to what game you are planning to write. If you want to do Doom III in.NET, you'll probably have to wait till computers with 5GHz processors and 2GB memory are common. Then again, everybody will agree with me that certain games just have to be written the hardcore C/C++ way. So what's the point of the question?
6. Summary:
If you are referring to using DirectX 9 with.NET like you do with Direct8 with C++ via COM interfaces, I think they are equally good, may be a bit slower due to the overheads.
If you want to do stuff like Diablo/Starcraft in.NET - as long as the user has sufficient memory I don't see why you can't.
Slashdot Mirror
I'm curious how ask slashdot has become a free goole answers service... The person asking the question should really do some research first.
.NET developer) hope so! But alas, I don't think the time has come yet.
.NET?
.NET. What's wrong with that? Honestly you don't need to optimize some part of the application, like the start-up screens or the options dialogue.
.NET. Check DirectX 9 SDK, you can use it with C#, VB.NET, etc. There are sample projects everywhere.
.NET Framework allows compiling down to native code, there is a .NET framework tool "ngen.exe" which generates a native image of your CLR assembly down to native code for YOUR machine - it will optimize for the particular processor. This is kept in the cache on the particular machine.
.NET, you'll probably have to wait till computers with 5GHz processors and 2GB memory are common. Then again, everybody will agree with me that certain games just have to be written the hardcore C/C++ way. So what's the point of the question?
.NET like you do with Direct8 with C++ via COM interfaces, I think they are equally good, may be a bit slower due to the overheads.
.NET - as long as the user has sufficient memory I don't see why you can't.
.NET please.
Some comments here:
1. Is it really the end of COM?
We (any
2. Will ALL Windows programming be done with
Sure, you can do the hard core stuff in [Unsafe] C#/C++, leave the rest in
3. DirectX is already available for
4.
5. I personally think it's down to what game you are planning to write. If you want to do Doom III in
6. Summary:
If you are referring to using DirectX 9 with
If you want to do stuff like Diablo/Starcraft in
Don't do Doom III in
jliu
>Dude, i could have registered a simlar domain and put up a comparable web page within a matter of hours. I hope they really exist.
Don't know if you'll survive a slashdotting though...
The same question comes across my mind the first time I read this, I thought perhaps Sharp is Sanyo's parent company...
After a brief check I settled with the fact that some people probably simply don't know one from the other.
Reminds me of Scott's eVest
I thought the message is more like:
If we screw up, don't get caught. If you get caught, you're gone.