Willem wrote:

The downside to using proprietary microsoft languages are that you are
at the mercy of microsoft in terms of support. A good example is vb6
which they decided not to continue supporting.

My reply:

Yes, that's true to a point. Although, to be fair Microsoft's C# .Net
language is no longer strictly speaking soully used by Microsoft.
There is the free and open source Mono Project that uses C# .Net as
its development language. So even if  Microsoft were to drop .Net
support and C# .Net tomorrow Mono would still be there. That's why I
would recommend C# .Net over J# .Net or VB .Net or some of the other
Microsoft specific languages.

That said, over all, i agree with you. Its not a good idea to use
proprietary languages and tools as Microsoft has a habit of pulling
the rug right out from under a developer when he or she least expects
it. When Microsoft decides to make a change they expect everyone to
change with them and everything you wrote in language x or using API x
be damned.


Gamers mailing list __ Gamers@audyssey.org
If you want to leave the list, send E-mail to gamers-unsubscr...@audyssey.org.
You can make changes or update your subscription via the web, at
All messages are archived and can be searched and read at
If you have any questions or concerns regarding the management of the list,
please send E-mail to gamers-ow...@audyssey.org.

Reply via email to