Ste wrote
c# is the future
Hmmm, I've heard that claim before - last time I think was when JAVA hit the market.
I'm not disputing C# is particularly suited to certain tasks, after all most programming languages have strong areas (personally I always found Delphi was really good for working with databases for instance) but I do think calling it 'the future' is a bit of a leap - especially as it is part of (and therefore tainted by) Microsoft's latest wheeze, the .net framework.
Before anyone accuses me of being blindly anti-Microsoft, I state here and now that I think Microsoft have produced some truly great products over the years, the 'classic' VB concept was (and remains) truly brilliant, VB3 through 6 being probably the most useful and almost certainly the most used programming tools since the introduction of GUI based computing.
They've also done some really good applications over the years. MS Office which is the world's most dominant productivity software
is good, though I have to admit preferring Lotus's SmartSuite because Lotus seems to have mastered upward compatability far, far better than Microsoft ever have. You might say that's no 'big deal', but consider this first;
I have many Lotus Macro language based worksheets written in 1990 (and earlier) in Lotus 2.4 / 3.0 (DOS based) which still work unaltered in the latest version 9.8 software. Excel based solutions seem to need re-writes with every new release. If you've built and now have to maintain many hundreds of applications, this becomes a very 'big deal' in a hurry - trust me on this.
That's all by the by, Microsoft's biggest problem with .net generally is the millions of disgruntled Visual Basic programmers out there who've invested years (in some cases many many years) in becoming expert in VB, who now feel MS has decided that they should just dump all the knowledge they've accumulated and start all over again with .net in the form of VB.net.
(Actually, VB.net isn't THAT bad to change to, if you already know another language like C++ or Java, but it IS a bitch if your knowledge base is in VB alone. Most people I know feel you might as well just learn C++ anyway as try to go from Classic VB to VB.net from a purely VB background)
Visit the related forums and you'll see there are a lot of very unhappy working professionals out there who's faith in Microsoft has gone, who are saying 'why should I bother to invest my time in learning .net, Microsoft will probably just dump the whole thing in a couple of years anyway. After all they've done it to me before with VB classic'.
It's not hard to see their point really.
C++ isn't a purely Microsoft product, C# effectively is. If you've just had your fingers burned by trusting MS and have to invest a lot of time in learning something new, would you hitch your wagon to the already proven C++ (cross platform, cross vendor) chariot, JAVA, or Microsoft's newest proprietary language that they could drop on a whim whenever it suited them, C#?
Were I a betting man, my money would
not be on C#. So in light of the above (more than any technical shortcomings) I can't see C# as 'the future', until MS proves otherwise I'm more likely to consider it just another MS variation on a mainstream language that I don't want to waste too much time on.
Al (MaDbRiT)