Anybody who suggests HTML as a language can't be serious: it's a /markup/, not a /language/.
I was actually going to suggest SQL as worthy of study. Not so much the data storage and recovery side, but the ancillary stuff which people have (perhaps unwisely) shoehorned into various problem-solving scenarios: using "classic" SQL (i.e. no scripts with looping etc.) to solve resource allocation problems etc. In this sort of context it appears to have a lot in common with APL: generate sets, look for intersections and so on.
The point I'm trying to make here is that there's two ways of looking at the "next language" question. If it's purely a case of "pick a useful language" then- regrettably- the answer has to be Python, or possibly C, FORTRAN or COBOL based on how much legacy code is floating around.
However I prefer to look at it from the angle of "how can I improve my intellectual toolkit", and from that POV it's valuable to look at alternative problem-solving techniques: even if the languages that exemplify them are niche or- as in the case of APL- derided.
As such, I would suggest that you might find the first few chapters downloadable from
https://web.engr.oregonstate.edu/~budd/Books/leda/ of interest. As an experienced programmer I don't think you'll find them particularly heavy going, and they might help crystallise your ideas of what you're actually looking for.
MarkMLl