…what about just being a “versatile non-strict functional language” ?
While not as glamorous, there is still some interest in “smoothing rough edges” - in addition to web services and APIs e.g. Servant:
https://discourse.haskell.org/t/using-unsafeperformio-safely/4146
-
https://wiki.haskell.org/Partibles_for_composing_monads
(my own work: experimental, based on personal experience and opinions!)
For an average person, investment in Haskell is not even «questionable» — it is not on the table. It is far easier to become a Solidity or JavaScript developer […]
After some time, they are frustrated by e.g. “the JavaScript problem”, which drives them to look for alternatives, such as Elm. The stark difference between those two languages must intrigue some at the very least, who then look a little further…or maybe not; if I could usefully predict the future, I would have permanently solved “the day-job problem” a long time ago!
…ouch! Then again, we have also been spoilt for choice with regards to Haskell extensions. Either way, it’s definitely a problem, as shown by (the absence of) Haskell 2020.
Since “Haskell burnout” was briefly mentioned:
https://discourse.haskell.org/t/what-happened-to-lightweight-concurrency-primitives-for-ghc/3363
…it does happen. But as @rae showed, it isn’t limited to Haskell.
Can things be better? Of course, but we should also remember that things could also be worse - some thirty-five years ago, a group of very-learned folk may have been too busy to realise that having one language was (at that time) simpler that several, for research and educational purposes.
In spite of the advent of multi-core desktop computers for everyday use, the prevailing paradigm is still imperative - that Haskell is now where it is in such an environment certainly looks like a success to me. As to it’s future…the worst-case scenario is that Haskell joins the ranks of Prolog and Miranda(R), to be used in education to awaken the imperatively-habitualised to alternate possibilities.
Anything more than that is a bonus.