Ask Slashdot: What's New In Legacy Languages?
First time accepted submitter liquiddark writes "I was listening to a younger coworker talk to someone the other day about legacy technologies, and he mentioned .NET as a specific example. It got me thinking — what technologies are passing from the upstart and/or mainstream phases into the world of legacy technology? What tech are you working with now that you hope to retire in the next few years? What will you replace it with?"
Perl rocks (Mojolicious, AnyEvent, Moose)
I've been playing with computers since the mid-70's and one of the things that I did early on was learn to program in C.
One of the smartest things I've ever done; it's up there with my decision to start running Linux in the late 90's.
If you can program in C you can write a program that runs on pretty much everything that you'll come across that you might want to program.
Learn C if you want to learn a programming language that you can use for a very long time.
I like Android, got an Android phone and a couple of tablets, but the C NDK doesn't allow you to do things without having to jump through a bunch of Java hoops to get there. I would have more Android devices if it was easier to write a program on it in C.
["hip","hip"]
(Hip hip array!)
If you're a zombie and you know it, bite your friend!
Apparently the writer of the original article thinks "legacy" means that you have to maintain and enhance existing applications instead of developing new ones.
To me, "legacy" means that there are no new applications being developed in that language, and the only jobs available for it are maintaining and enhancing existing applications. .Net and Java are certainly not "legacy" in that sense by any stretch of the imagination.
I do not fail; I succeed at finding out what does not work.
Why was .Net mentioned as a legacy technology? Its actively developed, has a decent community, and is widely used - apart from some poor articles and conclusions that were jumped to here on /. There is no reason to consider .Net a legacy technology.
What is more likely is that the person was referring to projects that are stuck on specific versions in maintenance hell, which can happen with any language - Ive been stuck with VB.Net 2.0 WebForms projects, while at the same time I've been using MVC 4 and .Net 4.0. One I would consider a legacy project, the other not, but both use the same line of tech.