Live data from Hacker News

Ask HN: What “old” programming languages will you still be using in 2017?

news.ycombinator.com

61–70 of 502 posts

Re: Ask HN: What “old” programming languages will you still be using in 2017?

#62
I really want to write something in 6502 assembly this year. I've read tutorials and played with it, but I've never used it to build a non-trivial program. I've also been wanting to build a NES emulator in common lisp, and this would be the perfect opportunity to pair the two projects.

Re: Ask HN: What “old” programming languages will you still be using in 2017?

#63

Pascal/Delphi Before there was an internet of lightbulbs and smoke detectors, there was an internet of industrial process things. And they used windows 2000 and Delphi. They still do.

My company has a multi-million-LOC application directed at medium to large healthcare providers written in FreePascal. I have worked with a lot of different codebases, and this is by far the best one. I would like to say it is because I have been the code dictator since it's inception, but it is probably because things are quite easy to structure using pascal.

Re: Ask HN: What “old” programming languages will you still be using in 2017?

#68
Mostly, I'll be writing a lot of fairly old fashioned C++ (my current project is yet to use a single smart pointer or lambda, lots of templates though) for high performance numerical work.

Also, I guess writing code in Python 2 is considered outdated nowadays, so that too. Plus the usual shell scripting (bash on Linux and simple batch files on Windows).

I do hope to avoid writing any new Fortran this year, so there's that. Some of the less performance critical code will instead involve Julia, and I've been experimenting with D and Rust for fun. Not sure which category Java and C# fit in, but in all probability I'll also use those at some point.

And finally, LaTeX. Very old and, unfortunately, indispensable.

Re: Ask HN: What “old” programming languages will you still be using in 2017?

#69
post #55
post #20

Writing a brand new Mac app for myself, using Objective-C instead of Swift. So far it's a breeze. Yes I used Swift for a while, and it sure feels all academic and all, but meh, ObjC gets the job done just fine for me.

Objective C will always have room in my heart, but I'll never go back to it. There's too much .h ceremony.

Meh, I've spent about 20 hours on this project so far, and I'd estimate probably 2 minutes of that time was spent managing .h files.
Post reply on HN