Do you mean haskell could already be considered dead?
o_0 …where did that other Abab9579 go?
Since you’re apparently no longer convinced by all the other responses, ask those who have gained experience with dead programming languages:
…just let the rest of us know what they tell you.
There could be another reason:
…this is the 21st century after all, when everything was supposed to be awesome; instead, it’s more resembling a dystopian callback continuation of the 20th, with a sprinkling of some nice techno-trinkets.
Oh. I mean, I interpreted their message being intended as “haskell is practically dead”. So I was asking for the intention/their thoughts. I guess it is quite hard to express my intention in short words while on mobile… sorry.
I myself don’t think haskell is dead.
No I mean we never so consciously said “OK research is done, it’s stability time!”. So it seems to hard to believe that Rust is “the place for language innovation” — there is the one time novelty factor trying out such a new language sure, but we have plans to keep on changing, whereas they do not.
I see. Sorry for misunderstanding… Though, did haskell language change by much? It seems like only refactors have been happening.
Specifically in this case there’s a discord community of haskell gamedevs that I know of which is somewhat active. I also know of another small community of people who like to write compilers in Haskell. It is possible that there are other such communities that no longer interact with the central hubs (e.g. reddit).
Haskell is indeed dead, and so is Common Lisp, in the same way that if someone is falling through the air and opens their parachute they stop falling and shoot straight up - it’s all relative. Python, for all of its faults, is making major advances in its share of programming time.
Alas poor Haskell,
I knew it, Horatio,
A language of infinite jest;
I absolutely agree. I don’t think Haskell will be able to substantially grow or keep its edge through new language features. We’ve been long beaten by Idris, Agda, F* etc in that domain and much of the community has a somewhat collective burnout from the constant change as has been attested by several non-trivial industry users.
The way forward is stabilization, improving performance and platform support. We’ve had many threads about this topic here and I feel most of the community agrees, but a couple important key people in the community do not. So there’s some things to figure out. Whether the HF stability working group can deliver a united front in that regard that’s actually backed by the board and GHC devs remains to be seen.
More resources on haskell gamedev.
There is a friendly community on Matrix, (bridged to irc if you prefer: libera.chat/#haskell-game
). Allure of the Stars (~50k LOCs, not a toy) dev Mikolaj dwells there.
Having used Haskell to write a small game (and a jam entry), I found the experience pleasing but yes some additional resources (documentation on best practices on how to set up your game, best way to structure games with lots of sub/minigames, etc.) would have helped.
I don’t have any factual argument as to why Haskell isn’t dying, but to go against what seems to be the common pattern in this thread of feeling like Haskell is dying and is beat, I must say:
I feel enthusiastic about Haskell every day, I feel like it’s such an amazing language that keeps on growing and being yet more amazing. I discover awesome and mind bending things (e.g. Control.Monad.Tardis) every day. I am that guy who won’t shut up about Haskell and keeps trying to teach it to his colleagues (and actually to just about everyone else).
I’ve recently started contributing to GHC after having read Trees That Grow – and now I’m even more enthusiastic about it – I’m excited for Haskell to be more modular – for it to be extended in new ways.
I’m excited for the upcoming in-person events like ZuriHac.
I’m seeing more attempts to bring other mainstream parts of programming into Haskell such as cross platform front end development (GitHub - obsidiansystems/obelisk: Functional reactive web and mobile applications, with batteries included.), and virtual doms (https://haskell-miso.org)
Yes. I am biased. Yes, I am in the Haskell bubble, but I mean to fight (ง’̀-'́)ง the negativity trend.
All possible graphs tell us that the Haskell community is growing at about the same rate as the market for programming languages, so its share of the market is not changing.
But the attitudes do change. No one wants to hear about Fancy Haskell and Category Theory anymore. No one is thinking that Haskell is the solution to those problems everyone is suffering from every day: crashes, lags, death by complexity. Haskell is not seen as a general purpose language anymore. This is a stark change from what I recall from, say, 5 years ago.
I am not sure what the ethos is now. The passion is gone, what is left is established business. Cryptocurrency — yes, web servers — yes. Computer games, graphics, music — not anymore. There is no passion to break into data science and machine learning, even though it seems like Haskell could contest a share of that market. Most importantly, there is no spirit of exploration. There is seemingly nothing left to learn.
Some proponents of Haskell in this conversation (say, Tom Ellis, Richard Eisenberg) I know to be at the center of the industry. They are somewhat extroverted, very conscientious, very well off, their position on the market is lifelong. This is survivor bias at its finest. Others (Vanessa McHale, Julian Ospald) are no less successful I reckon, but even then somewhat cynical now — their messages bear an ever so slight shade of regret.
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, and the pay seems to be even better on average. No ethos other than economic efficiency is evident. No one is going to come.
And truly I see few unfamiliar names even in this conversation.
I think there’s quite a lot to be done, actually! Some things I would like to see (Haskell-exclusive?)
- FFI in the (lazy?) ST monad. I have questions about safety + explanations of why it is safe!
- More laziness! Stuff like doubly-linked lists, laziness for graphs, laziness for more elegant algorithms.
- A replacement for Template Haskell (might need some sponsorship at this point oof)
x86-64bit: Runtime code generation for x86 64 bit machine code is intriguing, actually uses the tardis monad for an assembler.
I think there is still joy to be had in little one-offs, I guess ambitious projects are not taking center stage as they once were…
To be fair, we did try. This was initially (2016) spearheaded (and the domain is still paid for) by Theam , then a small but active community grew around it, I was very active as an editor/hype man for the community (including running a workshop at ICFP’17 and pulling people in at ZuriHac and Haskell Exchange), we started building things, but then it sort of fell apart, people disappeared and the project ground to a halt.
And this is not meant to take credit from the crazies visionaries who have built machine learning libraries in this language. DataHaskell was simply meant to organize this effort. I have theories on why didn’t succeed (yet?), certainly have my share of the blame for not coordinating communications more effectively.
But the truth is that this stuff is super f+++++g hard to start with, it’s a lot of unglamorous work and additionally when you put 5 Haskellers in a room you get 12 alternative APIs for doing even the simplest task. We are simply allergic to standardization.
Oh man I forgot about HLearn… very good/cool stuff.
What are your thoughts on TH and why do you think it needs a replacement?
One far away goal for TH is to share the AST with Haskell (we’re working on TTG for that goal)
If you think it’d be an interesting discussion do open a separate thread.
-
Template Haskell eats children for breakfast.
-
https://taylor.fausak.me/static/pages/2018-11-18-2018-state-of-haskell-survey-results.csv.zip
…there probably are others.
Do you think that is something to be fixed?
Is any language a truly general purpose language though, if you consider how it is used? Also tbh, web is the too big of a domain nowadays to disregard. My thoughts were more about how companies involved in haskell has dwindled out, and with it, many haskell communities.
Because vanilla Haskell can be used to manipulate (not a separate macro language), you don’t separate runtime and compile-time nicely. Among other things this hopelessly breaks cross-compilation: What Template Haskell gets wrong and Racket gets right : ezyang’s blog
…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.