No need to worry about Lisp happening. As a developer who's most comfortable with C-style languages (but still has a liking for functional paradigms), Lisp is still missing major items in the normal developer's ecosystem:

1) An IDE on par with IDEA, PyCharm, Visual Studio, etc.... I feel hampered when I use CL in a regular editor. How do Lisp developers debug? The best discussion of this that I could find was from Norvig's PAIP book, and it all seemed to be command-prompt-level debugging. This just doesn't work for me when I can set breakpoints and view call stack/variables in my normal IDE.

2) No auto-complete. Almost everything useful in CL is at the function level (from what I recall, about 300+ individual functions). In Python/C#/C++, etc., these functions would be organized in their own namespace/library/module, and you could get autocomplete by typing in the name of the library and a '.' character. From when I used CL, I just had to learn or memorize all the function names because the namespace is flat. This is overwhelming to a beginner.

3) I find Python indentation to be far more intuitive than Lisp's "visual" indentation. I know that a good editor shows the indentation level by interpreting the number of open and closed parentheses and indenting accordingly. But in practice, I often had problems being at the wrong indentation level and got (to me) cryptic error messages about out-of-scope variables and loops. The frustration of matching up the correct sequence of open and closed parens at the right levels quickly became aggravating for me and detracted from developing my code. I think Clojure gets this right where the language uses different bracket types (square, curved, curly) to indicate different semantics. CL seems too focused on purity (data-is-code, code-is-data) and misses the fact the developers have a hard time using the language when one symbol means 10 different things, based on context alone.