"Those in search of eternal life need look no further than the computer industry. Here, last gasps are rarely taken, as aging systems crank away in back rooms across the U.S., not unlike 1970s reruns on Nickelodeon's TV Land. So while it may not be exactly easy for Novell NetWare engineers and OS/2 administrators to find employers who require their services, it's very difficult to declare these skills -- or any computer skill, really -- dead." My Take: "C" dying should have been "x86 Assembly".
To read all comments associated with this story, please click here.
Member since:2005-07-06
"Maybe he forgot VS is written in C/C++"
VS is written in an mixture of C++ and .Net actually, and has full managed bindings to the automation API. Regardless, what does VS written in *insert language here* have to do with writing .Net code?
Furthermore, if you're a Windows developer, then .Net has indeed changed the world. For the better. I haven't written a single line of VB6 or unmanaged C++ in years, and hope to never have to again.
Member since:2005-10-08
> Furthermore, if you're a Windows developer, then
> .Net has indeed changed the world. For the better.
> I haven't written a single line of VB6 or unmanaged
> C++ in years, and hope to never have to again.
Which is fine, as long as you do not have to write applications to run on older hardware, and do not care about cross platform capability at all.
When it comes to older hardware, .NET has all the problems that Java has. It uses too much memory, it loads classes dynamically at runtime when they are needed (which is slow in general), etc.
When it comes to cross platform capability, Java clearly kicks C#'s ass.
So basically, for me, I use Java when absolute speed / performance doesn't matter, or when I don't have to worry about supporting older hardware. Otherwise I use C. I have no use for C# (Windows only for all practical purposes, since mono will never be fully compatible). I also have no use for C++, since it doesn't offer me anything that C or Java doesn't. C++ is basically an example of how NOT to write an OOP language.
Member since:2006-06-09
For the "better" because the previous Windows API sucks big time. It's not because on a platform the C or C++ API was bad that is the same on all other platforms, or the language was/is the only one guilty.
People does great [embedded or not] operating systems and API in C/C++, making developers life easier. Microsoft just didn't with win32. Maybe they didn't/don't care that much because it's better for them to control everything, API *and* language *and* development toolsuite, and the hardware manufacturers are always happy to have a selling point for their ore powerfull CPUs and bigger memory chips...
Member since:
2007-03-08
I laughed nice when I read the article.
I work with C at a company witht 5k+ employees where C is the main language. C is not dead and it will not be for long.
The article is probobly written by one of those .Net coders that think .Net is gonna change the world. Maybe he forgot VS is written in C/C++ =)