Ok time so set some of these misconecptions straight. 1 as long as we have dll's we will have com thats how things work. The next version of windows will actually keep multiple versions of dll's so i dont see how we are getting rid of com any time soon. 2 You can compile un-managed c++ in vs.net 2003 I know for some people the.net is all they see but guess what. DONT USE MANAGED EXTENSTIONS IN C++ IF YOU DONT WANT IT TO BE MANAGED.... To compile to native code in vs.net2003 for c++ you just dont use managed extensions and then you set one compiler flag and Viola you have a win32 native binary. a win32 application is even an option in the new projects menu.
3.DirectX 9 is both managed and unmanaged. I cant say this for absolute certinty but I believe that the only thing the managed extensions for DX9 are is a series of wrapper classes which makes use of the DX9 dll and lib files. WHich would once again be com. We also have to realize that dx has applications outside of game programming also. The only thing dx is(which isnt a small thing) is a set of wrappers to access hardware, You cant even call them classes because of com. It just makes it so you dont have to worry about 5000 different joysticks when your programming an app. Granted OpenGL is better for graphics than dx. HOWEVER you dont have input libraries/sound libraries/networking libraries in OpenGL.
TO a comment earlier that said c# is an immature java. I say that statement is entirly off. Ive been programming java for about 2 1/2 years and c# since its initial beta days. Ive worked with a large portion of the JFC and the BCL and I can tell you that the BCL is far nicer to work with. There are things that are totally missing from java like say a representation of a 3d point? or how about a datastructure that represents a cube. both are very simple things that are found nativly in the BCL. Windows.Forms put swing to shame and there are no tools out there that compare to vs.net. Its a superior ide on most levels. Also while it retains some syntactical similarities to java c# is far from being a java clone. C# has what I like to call smart properties which actually can use left and right assignment justification as opposed to java with all the get and set method stuff. Its a waste. Lets see ohh also no operator overloading in java..... But wait its in c#. The bigest thing of all POINTERS. In c# you have access to pointers while java totally blocks them off. A major point I see over java which made a stupid mistake about this in the first place is.... In c# everything is an object and can be placed into a container. Those who have worked in java know the pain of having to store characters in a vector by doing
Character myChar = new Character(myCharVariable) charVector.add(myChar); wouldent it be a lot easier to just do charVector.add('a');
Well java had performance issues with doing it that way. Which I should be grateful they did it that way since if java got any slower it would be unusable.
Well thats some fact and some opinion ill let you sort out which is which. Its also nice to know that in a year and a half c# has provided more functionality and an easier to use set of class libraries than java has since its existance (something like 10 years if im right)
Slashdot Mirror
Ok time so set some of these misconecptions straight. .net is all they see but guess what. DONT USE MANAGED EXTENSTIONS IN C++ IF YOU DONT WANT IT TO BE MANAGED.... To compile to native code in vs.net2003 for c++ you just dont use managed extensions and then you set one compiler flag and Viola you have a win32 native binary. a win32 application is even an option in the new projects menu.
;
1 as long as we have dll's we will have com thats how things work. The next version of windows will actually keep multiple versions of dll's so i dont see how we are getting rid of com any time soon.
2 You can compile un-managed c++ in vs.net 2003 I know for some people the
3.DirectX 9 is both managed and unmanaged. I cant say this for absolute certinty but I believe that the only thing the managed extensions for DX9 are is a series of wrapper classes which makes use of the DX9 dll and lib files. WHich would once again be com. We also have to realize that dx has applications outside of game programming also. The only thing dx is(which isnt a small thing) is a set of wrappers to access hardware, You cant even call them classes because of com. It just makes it so you dont have to worry about 5000 different joysticks when your programming an app.
Granted OpenGL is better for graphics than dx. HOWEVER you dont have input libraries/sound libraries/networking libraries in OpenGL.
TO a comment earlier that said c# is an immature java. I say that statement is entirly off. Ive been programming java for about 2 1/2 years and c# since its initial beta days. Ive worked with a large portion of the JFC and the BCL and I can tell you that the BCL is far nicer to work with. There are things that are totally missing from java like say a representation of a 3d point? or how about a datastructure that represents a cube. both are very simple things that are found nativly in the BCL. Windows.Forms put swing to shame and there are no tools out there that compare to vs.net. Its a superior ide on most levels. Also while it retains some syntactical similarities to java c# is far from being a java clone. C# has what I like to call smart properties which actually can use left and right assignment justification as opposed to java with all the get and set method stuff. Its a waste. Lets see ohh also no operator overloading in java..... But wait its in c#. The bigest thing of all POINTERS. In c# you have access to pointers while java totally blocks them off. A major point I see over java which made a stupid mistake about this in the first place is.... In c# everything is an object and can be placed into a container. Those who have worked in java know the pain of having to store characters in a vector by doing
Character myChar = new Character(myCharVariable)
charVector.add(myChar)
wouldent it be a lot easier to just do
charVector.add('a');
Well java had performance issues with doing it that way. Which I should be grateful they did it that way since if java got any slower it would be unusable.
Well thats some fact and some opinion ill let you sort out which is which. Its also nice to know that in a year and a half c# has provided more functionality and an easier to use set of class libraries than java has since its existance (something like 10 years if im right)