Linked by David Adams on Wed 1st Oct 2008 14:32 UTC
Microsoft's leader of C# development, writer of the Turbo Pascal system, and lead architect on the Delphi language, Anders Hejlsberg, reveals all there is to know on the history, inspiration, uses and future direction of one of computer programming's most widely used languages - C#. Hejlsberg also offers some insight into the upcoming version of C# (C#4) and the new language F#, as well as what lies ahead in the world of functional programming.
Thread beginning with comment 332059
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-06
Member since:2008-04-21
Member since:2005-07-06
C# is not a systems programming language, it is mainly a business programming language.
There isn't even a great deal of that going on. Most of the business code that has been written on desktops over the years has been mainly C++ and Visual Basic, and there is simply zero business case for anyone to rewrite code just so they can run .Net and program in C# and get applications that are functionally equivalent.
Anybody who has moved to something new over the years has moved to web based applications, mainly because they don't need to faff about with the client and all the costs and administrative pain that entails. MSDN magazine comes up with ever more creative ways of pulling in dependencies that will blow your foot off once you try and deploy it to users. At least web applications have had some return on investment.
It doesn't make any sense whatsoever to program core parts of Windows in C#.
Then why should anyone else use it?
Member since:2006-05-09
C# is not a systems programming language...
Why not?
Look at SharpOS:
http://en.wikipedia.org/wiki/SharpOS_(operating_system)
Member since:2005-11-09
Member since:2005-07-06
Member since:2006-02-05
Almost every business product MS has uses .net in some way, and almost every new product they make is done in .net. There is no real business case in re-writing most of their software from the ground up in .net for no other reason then maintainability and futureproofing, for them or for anyone else.
Member since:2005-07-06
There is no real business case in re-writing most of their software from the ground up in .net for no other reason then maintainability and futureproofing, for them or for anyone else.
Then why can't Microsoft's customers take a classic VB project, or a VC++ 5 or 6 application, open it up in Visual Studio 2008 and get it to compile and run in a .Net environment with very little, if any, code changes? Why is Microsoft asking their customers to do something that they themselves admit is a waste of time and money and is not backwards compatible?
Member since:
2005-07-06
Its been almost a DECADE SINCE Microsoft announced they were going to stop trying to pretend like they were going to use any standard version of Java, and moved to their own proprietary copy of the java concepts.
And yet..in all that time very little is actually using it in the Windows OS.
Makes you go hmmmm.