As their soundcheck question for 2024, Computerphile asked their
interviewees what their least favourite programming language was <https://www.youtube.com/watch?v=03lRzf7iSiU>.
The most popular answer was JavaScript, with 4 votes. There were 2
votes for PHP, and one each for Lisp and Python.
The Python-hater didnrCOt like dynamic typing. Given how many dynamically-typed languages there are (including lots older than
Python), how come Python was the first one he thought of?
As for JavaScript, I think itrCOs misunderstood. The only one who gave a reason for his dislike gave an outdated reason -- scope hoisting. That doesnrCOt have to apply any more, if you avoid rCLvarrCY declarations, and also use strict mode to avoid implicit globals.
I imagine PHP would have got more votes, if more people had had to use
it.
One mentioned COBOL (which for him was worse than Fortran), but nobody thought of BASIC. I guess that is now so far in the past, many among
the interviewees wouldnrCOt even have any memories of using it ...
One mentioned COBOL (which for him was worse than Fortran), but nobody thought of BASIC. I guess that is now so far in the past, many amongAnd/or that anybody using BASIC in a modern context is gonna be using
the interviewees wouldnrCOt even have any memories of using it ...
On Fri, 31 Oct 2025 06:48:08 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
One mentioned COBOL (which for him was worse than Fortran), but nobody
thought of BASIC. I guess that is now so far in the past, many among
the interviewees wouldnrCOt even have any memories of using it ...
And/or that anybody using BASIC in a modern context is gonna be using something like FreeBASIC, which is a vastly improved and perfectly
reasonable little language compared to the early microcomputer BASICs.
Re: Javascript, it's true that a lot of improvements have been made to
it, but from a certain perspective it's all lipstick on a pig; there's
been so many things slapped on to paper over some poor initial design decisions or chase trends in web development over the years that at
this point it's a fossil shale of a language.
Anyway, there's things to dislike about most any language, but there
aren't too many that I'd universally condemn in my own assessment.
Pascal gets a frowny-face for design decisions that should never, ever
have made it past the initial draft of the first paper (making array
size part of the type specification was braindead from the start - an impediment to good design *and* a burden on performance, all in the
name of avoiding a problem that there were much better solutions for,)
and while newer iterations have improved things somewhat, it would've
been better to throw it out and re-do from scratch...*but* the FP folks
do put a lot of effort into making it a full-featured and surprisingly portable platform for development.
Another language that feels needlessly gross and tedious is Java - it's
just *unreasonably* verbose, to the point where one is tempted to
employ a macro preprocessor just to condense sesquipedalian nonsense
like System.out.println() down to furshlugginer print() and so forth.
Re: Javascript, it's true that a lot of improvements have been made
to it, but from a certain perspective it's all lipstick on a pig;
there's been so many things slapped on to paper over some poor
initial design decisions or chase trends in web development over the
years that at this point it's a fossil shale of a language.
On Fri, 31 Oct 2025 06:48:08 -0000 (UTC)
Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:
One mentioned COBOL (which for him was worse than Fortran), but nobody
thought of BASIC. I guess that is now so far in the past, many among
the interviewees wouldnrCOt even have any memories of using it ...
And/or that anybody using BASIC in a modern context is gonna be using something like FreeBASIC, which is a vastly improved and perfectly
reasonable little language compared to the early microcomputer BASICs.
Re: Javascript, it's true that a lot of improvements have been made to
it, but from a certain perspective it's all lipstick on a pig; there's
been so many things slapped on to paper over some poor initial design decisions or chase trends in web development over the years that at
this point it's a fossil shale of a language.
Anyway, there's things to dislike about most any language, but there
aren't too many that I'd universally condemn in my own assessment.
Pascal gets a frowny-face for design decisions that should never, ever
have made it past the initial draft of the first paper (making array
size part of the type specification was braindead from the start - an impediment to good design *and* a burden on performance, all in the
name of avoiding a problem that there were much better solutions for,)
and while newer iterations have improved things somewhat, it would've
been better to throw it out and re-do from scratch...*but* the FP folks
do put a lot of effort into making it a full-featured and surprisingly portable platform for development.
Another language that feels needlessly gross and tedious is Java - it's
just *unreasonably* verbose, to the point where one is tempted to
employ a macro preprocessor just to condense sesquipedalian nonsense
like System.out.println() down to furshlugginer print() and so forth.
Any language that *requires* an IDE with weapons-grade autocomplete
deserves censure...but then it's somehow still the best solution we've
got for write-once-run-anywhere development, which is maddening :/
Also, absent additional analysis steps or similar, and thus code
complexity, full lexical scoping is prone to rapidly leak memory.
This is a non-issue with dynamic scoping, even if, potentially,
using dynamic scoping as the default is itself a foot gun (in terms
of semantics).
On Mon, 3 Nov 2025 14:05:12 -0600, BGB wrote:
Also, absent additional analysis steps or similar, and thus code
complexity, full lexical scoping is prone to rapidly leak memory.
You mean, you need to put call frames on the heap, not the stack? And
that will expose any lack of robustness in your memory-management
scheme?
By the way, Python is clever enough to only put referenced outer-level variables within the closure.
This is a non-issue with dynamic scoping, even if, potentially,
using dynamic scoping as the default is itself a foot gun (in terms
of semantics).
This sounds like a rCLI could implement it much more efficiently if I didnrCOt have to do it correctlyrCY kind of argument ...
Some of my past languages had both lexical and dynamic scoping (with
lexical as the default). This can make more sense.
And/or that anybody using BASIC in a modern context is gonna be
using something like FreeBASIC, which is a vastly improved and
perfectly reasonable little language compared to the early
microcomputer BASICs.
In one project, I ended up implementing a BASIC dialect partly
inspired by early Unstructured BASIC dialects. Though, in this case,
this was more because it allowed writing an interpreter in roughly
1000 lines of C.
Though, I ended up extending it in some non-standard ways that didn't
really match up with either 80s BASIC, or the direction the language
went in the 90s.
But, the use-case I had didn't really need it to go in the 90s
direction, and keeping the interpreter small also did not favor going
that direction (where the 90s dialects more went in the direction of
trying to turn it into a more general purpose programming language).
On Mon, 3 Nov 2025 14:55:31 -0600, BGB wrote:
Some of my past languages had both lexical and dynamic scoping (with
lexical as the default). This can make more sense.
Dynamic binding simply isnrCOt that useful. Lexical binding just works more naturally the way people expect.
Say, for example, if you had something analogous to stdin/stdout as dynamically scoped variables, then it makes IO redirection easy.
They can also serve a similar role as TLS variables (though, in a more advanced compiler, they were usually implemented as an additional local save/restore mechanism on top of TLS variables). In this case, the role
of dynamic variables can be overloaded to that of TLS variables.
The most popular answer was JavaScript, with 4 votes. There were 2
votes for PHP, and one each for Lisp and Python.
One mentioned COBOL (which for him was worse than Fortran), but nobody thought of BASIC. I guess that is now so far in the past, many among
the interviewees wouldnrCOt even have any memories of using it ...
Another language that feels needlessly gross and tedious is Java -
(...) but then it's somehow still the best solution we've got for write-once-run-anywhere development, which is maddening :/
I think that may have been true around 02001, when J2ME could run
more or less normal Java code on *all kinds* of fairly small feature
phones.
Android might be the main exception; it ships with an incompatible implementation of Java (without, for example, AWT), and although you
may be able to recompile Unix software for it, it can be difficult.
Unix doesnrCOt run on small microcontrollers, but C sure does. With
sdcc you can even run it on a PIC or an 8051, though you wouldnrCOt
want to.
This is a much less compelling choice in the last several years
since the Python maintainers have adopted a policy of deliberately
breaking standard library backward compatibility in every point
release.
Another language that feels needlessly gross and tedious is Java -
(...) but then it's somehow still the best solution we've got for write-once-run-anywhere development, which is maddening :/
I think that may have been true around 02001, when J2ME could run more
or less normal Java code on *all kinds* of fairly small feature
phones. But it never made the leap to smaller microcontrollers like
the AVR, feature phones evaporated, feature-phone-sized micro-
controllers never acquired J2ME support, and now in 02026 we have a
number of better solutions: C under Unix, portable C, Rust, Python, JavaScript, Wasm, Godot, and Golang.
Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
But J2SE was available in an open-source form, namely OpenJDK. So
they adapted that instead.
With respect, I think you may have gotten this wrong. Originally
they used Apache Harmony (presumably they preferred its non-copyleft licensing) but switched to OpenJDK in 02016 in response to the
Oracle lawsuit <https://arstechnica.com/tech-policy/2016/01/android-n-switches-to-openjdk-google-tells-oracle-it-is-protected-by-the-gpl/>
On Thu, 27 Aug 2026 21:11:55 -0300, Kragen Javier Sitaker wrote:
This is a much less compelling choice in the last several years
since the Python maintainers have adopted a policy of deliberately
breaking standard library backward compatibility in every point
release.
In what way?
They call it rCLremoving dead batteries from the standard libraryrCY ...
This makes it easy to encounter situations like this poster about
KittenTTS did, who says all of their Python versions on their various machines are either too old or too new: <https://news.ycombinator.com/item?id=44808718>
Contrast the stance of the Golang development team: <https://go.dev/doc/go1compat>
However, their motivation, understandable though it is, is irrelevant to
my point, which is that as a result of this policy, Python has, in
practice, gone from being one of the *most* portable languages to one of
the *least*; you canrCOt even reliably run a Python application you wrote
on Ubuntu 25.10 (Python 3.13) on Ubuntu 26.04 (Python 3.14).
Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
Does anybody still want to use the rCLcgirCY module?
Yes. Although CGI was pretty costly when it went out of style in the
01990s, hardware has improved dramatically, and CGI can now handle
half a billion hits per second on one server <https://jacob.gold/posts/serving-half-billion-requests-with-rust-cgi/>
which is enough for all but the biggest public websites.
I have three or four CGI scripts written in Python that IrCOve been
using for many years without having to maintain them.
Sun rCLaurCY file format?
Yes, obviously? There are plenty of audio data files from 30 years ago
in .au format.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:41:20 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,582 |