C# is the past, the present and the future

Re:C# is the past, the present and the future by damian2000 on Friday January 11, 2013 @06:34AM (#5042255)

I love C# as much as any MS fanboy would, but when people like Charles Petzold start abandoning C# and .NET for native C++ - http://blogs.msdn.com/b/msdnmagazine/archive/2013/01/08/1038... - to get more speed out of Windows 8 apps, then you have to start thinking maybe Microsoft is at least pushing C#/.NET out of the limelight - its not the be all and end all it used to be.

[ Parent | on HN ]

Re:C# is the past, the present and the future by jinushaun on Friday January 11, 2013 @06:43AM (#5042272)

That's like saying Ruby is dying because some people choose to implement some gems in C++, which is a ridiculous thing to say. Pick the right language for the job: rapid development versus raw performance. They can coexist.

[ Parent | on HN ]

Re:C# is the past, the present and the future by barking on Friday January 11, 2013 @06:54AM (#5042308)

Second question down in that interview in response to petzold mentioning C++ :

Desmond: So should we be looking to move away from managed platforms and languages?

Petzold: No, no, no, not at all.

[ Parent | on HN ]

Re:C# is the past, the present and the future by dromidas on Friday January 11, 2013 @03:13PM (#5044711)

Not everything needs native C++ performance. I use C# all the time on things that need easy maintainability and to be as secure as I can reasonably make it.

[ Parent | on HN ]

Re:C# is the past, the present and the future by damian2000 on Saturday January 12, 2013 @09:28PM (#5049735)

Totally agreed ... horses for courses etc. I also use C# the majority of the time ... but it seems like it will now be sharing the stage with C++ and possibly HTML/JS in terms of the recommended languages by MS.

[ Parent | on HN ]