As to companies not upgrading... sheesh. We should probably just use cobol(or worse if possible) and code on paper so the typists can copy it onto punch cards for the big shiny boxes which need to be dusted 6 times per day. But then again, if output only needs to be one debugged line a day, it's not all bad..
Or maybe we should just all switch to
intercal and say goodbye to any sanity.
I really should say something sane now, though I still feel like ranting, so I'll try to hold back.
The C++ boys are racing ahead, .net is playing catch up, and needs to overtake in every field to win - and they have numbers. Luckily .net has a few advantages of it's own.
DX: Stick to the new 2.0 assembly - it is cleaner and much easier to use, especially for new projects. (I've not checked the irrlicht source, but converting any COM interfaces they might still be using to .net 2.0 will probably be a nightmare)
Development: Stick to .net 2.0 - the .csproj is compatable with visual studio 2005 and the express versions... keep solutions in express, everyone has access to that and it seems unlikly that everyone has the full version.
I do not want to see this project fail or put anyone off - but
today I'd be happier with custom objects/nodes, better animation and the like with the existing wrapper.
Tommorow on the other hand is another thing altogether and I probably wouldn't mind helping out a little on something that doesn't involve screaming at multiple layers of C++ code.