After spending some time munching over the problem I have come to the conclusion that – fanboise excluded – there is in fact very little one can say.
C#: designed by Anders Hejlsberg, father of Delphi and [large chunks of] Turbo Pascal, ditto J++ and Windows Foundation Classes.
Make no mistake, this guy knows what he is about, and is backed by a company that pretty much dictates what the PC world is going to do next.
Emphasis ‘next’: he knows what Santa is bringing us for Christmas in 2015.
C# is a great language to use, especially with the improvements to the IDE, the support via CodePlex etc.
As an example, ‘Hello world’ now only takes 20 minutes . After three days of meeting as to how best to present the text, which database connection type to use etc.
Microsoft’s websites are – in total – the biggest in the world. And they work very well.
If you are building a big website – and you have the budget [just check the current price of Visual Studio 2010 Ultimate with MSDN - Ferraris are dirt cheap in comparison. And then there is the training] – then there is no argument.
And it ain’t PHP.
PHP (of which I know f*-all) : fathered by Rasmus Lerdorf: in comparison to Anders, a ‘talented amateur’ (btw not meant to be derogatory).
The development appears to have focussed on getting results, rather than a long-term focus**. The result is the hodge-podge that provides ample ammunition for the decriers.
Version 5.x appears to have implemented most of the requirements of an object language.
However, given the lack of long-term focus (** above) – plus the fact that many of the initial PHP users were not trained programmers – my guess is that PHP will (for the foreseeable future) suffer the same stigma that
‘BASIC’ does. (Very few know that Visual Basic was widely used at NASA. Or that Microsoft’s Professional Basic for DOS turned out code that was as fast as their C compiler)
Where does that leave us ? With the fanboise fighting, which should be viewed as a good thing: that way they don’t interfere with those of us who work for a living .
BTW, the risks are probably bigger when going the Microsoft route. We are in the middle of a big development using Silverlight . which Microsoft have now decided will no longer be actively supported .
And the latest version of our IBM iSeries operating system – V7R1 – mentions as an aside (about page 70) that the SQL Query Optimiser has been completely re-written. This has a couple of minor side-effects that it is suggested we should learn to live with ASAP:
1. All SQL statements should be re-tested to see if they still work; and
2. No, IBM does not have any tools and / or suggestions as to what to look for .
Reminds me of the days when banks were respectable .