Live data from Hacker News

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

news.ycombinator.com

421–430 of 502 posts

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

#421
post #415

Java and C#, with a bit of (MS)SQL and ASP.NET and a smattering of VBA and ASP at work. None are what I would consider "old". For fun, though, there's QB64's implementation of QuickBasic. I also have my old 8088 up and running again, and GW-Basic and ASM there. I started with GW-Basic when I was about 4 years old on that old 8088. Two 5.25" drives, no HD, 640k RAM and a "Turbo" button. What's not to like? Co-worker i…

I think I read somewhere COBOL has >300 reserved words?

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

#422

Many folks have said it here but I'll say it again: Common Lisp. I have been using it professionally for 5+ years as a full-time employee at various companies. Some big-name ones, some smaller start-up ones. The mean Lisp team size has been around 4, but I did work on a project of 15 Lisp programmers. None of these projects were legacy code. Some were in places you wouldn't expect (embedded, multi-processor systems o…

Are there resources you'd recommend for finding jobs in CL ?

The canonical site is https://lispjobs.wordpress.com/

Googling, LinkedIn searching helps.

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

#423

Many folks have said it here but I'll say it again: Common Lisp. I have been using it professionally for 5+ years as a full-time employee at various companies. Some big-name ones, some smaller start-up ones. The mean Lisp team size has been around 4, but I did work on a project of 15 Lisp programmers. None of these projects were legacy code. Some were in places you wouldn't expect (embedded, multi-processor systems o…

Slime + emacs for your environment?

Yep, all the way. Slime + Emacs + Paredit.

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

#424
We still have a whole lot of FORTRAN77 around at my work that I will do some work on. Some of it is very close to FORTRAN-IV. These are Gen-IV nuclear reactor simulation codes written by Argonne National Lab and friends mostly in the 1960s-90s. They were validated against experimental facilities back then and therefore have a good pedigree. Since most of the experiments are no longer operational and not all the results and test conditions were well documented, it's a challenge to update. We've upgraded some of the memory management stuff through the years at least and there's more FORTRAN90 every day, which is a nice modern language from this perspective.

Thankfully we have written gobs of Python to do most of the data management, multiphysics coupling, multiobjective optimization, etc. so it's really not too bad.

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

#425
DCL[1]: scripting builds on a long obsolete version of OpenVMS which doesn't even support command line piping, on half-baked Alpha servers loaded via 130mm magneto-optical drives over SCSI for hardware test programs written in...

ATLAS[2]: an utterly repulsive, "self-documenting" language designed specifically for test applications, which has somehow managed to outlive the demise of its guiding IEEE standards committee to the dismay of many a aspiring young engineer. Paradigms include 20+ token statements as a sensible method to toggle a switch best described as abusive by certain alumni of aforementioned committee; proliferation of subsets which aren't even notionally interoperable because it makes people feel special; and nerfing canonical features related to trivial GPIO control only to adopt a proprietary language such as...

L200[3]: because languages are always fun when comma delimiters are strictly optional most of the time, and it's easier to metaprogram an application than to actually write it. Build/runtime/debug environment is also fun when it's technically an obsolete filesystem emulator executed by an obsolete OS running on an obsolete hardware architecture whose performance[4] pales in comparison to a 1st generation RPi.

[1] https://en.wikipedia.org/wiki/DIGITAL_Command_Language

[2] https://en.wikipedia.org/wiki/Abbreviated_Test_Language_for_...

[3] https://en.wikipedia.org/wiki/Teradyne

[4] http://xkcd.com/303/

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

#427

Earlier quoted context omitted.

You know, modern Fortran isn't awful. Fortran 77 code however, is frighteningly ugly to look at.

IMO, it's more than not awful , it's great! I wish I had picked it up sooner as a mid-level language for mathematical and scientific computing (over C++). Additionally, you can connect Fortran to Python dead simple with `f2py`.

IMO the ongoing trend of moving everything academic to C++ is just awful. I still don't get why everything thinks a language-to-rule-them-all is what should be used by default, especially in the age of LLVM. IMO Alan Kay and his research group has always had exactly the right ideas in this regard. I think iPython/Jupyter + Numpy + some kind of JITed Fortran 2008 environment with accelerator support would be a nearly ideal scientific computing environment. Basically a free, open source and blazingly fast (HPC ready) version of Matlab.

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

#428
post #213

Earlier quoted context omitted.

I am working on 20 years old codebase that runs accounting, warehouse management, time tracking, invoicing and whatnot monster that power most of the roofing companies in Austria. It is still Delphi 5 + Paradox, developed on Windows XP (I run it from VM on Mac), but work on modern Windows as well. Networking is a bit of problem, but nothing we can't deal with. On the other side, I don't think that Delphi/Pascal is de…

Not unsurprisingly, I'd much recommend getting rid of Paradox. For my projects (several 100KLOCs, most of it DB-related) I relatively easily migrated to Firebird with IBObjects ( http://www.ibobjects.com – not affiliated), both of which have been a major success.

Migrating db is on my list all 9 years I am working on project, but I still havent find a way to do it. Core of the problem is stupid idea that paradox tables are actually files, so there are tons of copying and moving files around instead of using paradox as db.

Given the complexity of project and our budget it will have to stay.

Post reply on HN