Linked by Eugenia Loli on Thu 24th May 2007 20:59 UTC
OSNews, Generic OSes "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".
Thread beginning with comment 243050
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: C dead?
by Simba on Fri 25th May 2007 09:32 UTC in reply to "RE: C dead?"
Simba
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.

Reply Parent Score: 2

RE[3]: C dead?
by jayson.knight on Fri 25th May 2007 09:54 in reply to "RE[2]: C dead?"
jayson.knight Member since:
2005-07-06

That's a good response save for one very important thing: None of the stipulations you mentioned matter in the realm of IT, mainly because it's a controlled environment. The choice in IT usually comes down to "what platform do we want this application to run on." If it's Windows, .Net is the obvious choice, with an occasional need for unmanaged C++. All other platforms usually get the Java nod.

"C++ is basically an example of how NOT to write an OOP language."

Modding you UP for this statement...I wish more folks thought like you do. Most of the C++ devs I know who moved on to Java/C# said the hardest part was unlearning the psuedo OOP principles they "learned" in C++, and learning not to fight the compiler ;-).

Reply Parent Score: 2

RE[4]: C dead?
by Soulbender on Fri 25th May 2007 11:33 in reply to "RE[3]: C dead?"
Soulbender Member since:
2005-08-18

"None of the stipulations you mentioned matter in the realm of IT, mainly because it's a controlled environment."

I think you mean corporate I.T and not I.T in general. When it comes to corporate/internal systems you do have that control but you do not necessarily have it outside that problem domain.

Reply Parent Score: 2

RE[3]: C dead?
by BluenoseJake on Fri 25th May 2007 15:21 in reply to "RE[2]: C dead?"
BluenoseJake Member since:
2005-08-11

In a business you write software for the platforms you have, not for everything under the sun. Therefore, if you are a Windows shop, or a mixed Windows/Linux shopped, C# or Java will do just fine. That's what systems analysts do, design apps for YOUR systems

Reply Parent Score: 2