>>538420
>is anti-meme
>says Forth and CL are (((dead)))
You probably won't get a Forth or CL job. If you 'program' by throwing partial wrappers of libraries together, then you'll suffer from having fewer wrappers than you're used to. If you program on the job, then for workforce purposes you'll be asked for something more commonly known. If you can only program by etching your initials into an established codebase, you'll find fewer oportunities for that. If you can't write hello world without copying and pasting code from stackoverflow, these languages are pretty hopeless.
So if that's what dead means to you then Forth is dead.
OTOH, if there is something you would like to do, yourself, then you can do it in Forth or CL. And if you know these languages you'll want to usr them because they're so much better than the alternatives. You'll probably have a good implementation for your platform and all the code ever written in these languages will still work for that implementation. You'll actually have implementation options that are usually not available - you can interface with the Java world with ABCL, or C with ECL. You can target mobile platforms with mocl, etc. SBCL has less runtime overhead than PHP if you want programs to start fast and it compiles to native code with an optimizer that can make inferences based on your type annotations. Forth has extremely low overhead in lina and SwiftForth, and extreme optimization in iForth and MPE Forth, and runs everwhere. You'll also find a community, alternately on IRC and usenet, and some good books.
Forth and CL are superior languages with superior implementations, and your code won't actually rot like it will with most other languages these days.
So if you've got shit to do, these languages are not dead. You can use them.
An actually dead language would be something like K, presented to and then snatched back from the world, with only an undocumented trade secret or a random github work for implementations. Or Hedgehog lisp, an internal work that was abandoned on release and replaced with some ML thing. A dead language is a language you can't use even if you know it and want to use it.
A closer insult to the mark would be "hobby languages", but a full expression of that would be a language that you only ever use at your own expense. A language that, when you reach for it, you say "it would make more sense to use X, but I just wanna use this language today". And I never feel like that when I use Forth. not much of a CL hacker. Right now I've got a suite of tools that I'm writing in Forth because I wanted them to be as fast as fucking possible. I'm doing CGI with Forth because I want to use $2/year hosting and shared hosting and make the most of the scarce server resources (infinite RAM, infinite disk, but stab yourself everytime you use a full CPU second. STAB YOURSELF.) without giving people sites that would get suspended the first time two search engines look at it during the same hour.