Ask HN: Which “old” programming language(s) you still use in your $DAYJOB? And what's your experience of using such “old” programming language(s)? Here “use” can mean writing new code, debugging/maintaing old code etc. |
Ask HN: Which “old” programming language(s) you still use in your $DAYJOB? And what's your experience of using such “old” programming language(s)? Here “use” can mean writing new code, debugging/maintaing old code etc. |
Using a rugged android phone is talked about and sat on, that's about it.
One of the common complaints was that a lot of the core library had inconsistent function signatures[1], did they ever fix that? Always seemed to me that it would be an unfixable problem.
[1] https://softwareengineering.stackexchange.com/questions/3254...
(although sometimes I prefer C++, and learning Rust is still on my TODO list)
Previous jobs, not so long ago: Fortran, C, BASIC
Maybe not “old” but most of those are solid legacy.
Ada 2012, for instance, is a significant update to Ada proper (better integrated support for design by contract, among other things). The next iteration (and its SPARK subset) is potentially closing some of the gap between Ada and Rust in the areas where Rust is presently "safer" (by some measure, here primarily memory safety) than Ada.
C++20 versus C++98 (what I initially learned) is a very different language (or has the potential to be) thanks to its greatly expanded support for certain modes of programming that C++98 did not offer. But its differences with C++17 are a lot smaller, so they're more obviously "the same" language.