Hacker News Reader

Comment by paulajohnson | Hacker News Reader

Thanks for this. A couple of points:

1: I'd have rated Haskell's concurrency as "best in class" thanks to its STM implementation. Other languages do have STM, but AFIAK only Haskell provides both efficiency and safety thanks to its type system. Other languages have to choose between tracking every variable (slow) and letting the programmer declare which values are going to be rewound if the transaction aborts (unsafe).

2: Your section on IDEs does not consider Leksah. I've just come back to this after a long time on Eclipse and Atom, and its now a mature IDE specialized for Haskell. You might consider bumping Haskell to "mature" based on this.

View on HN

I agree on concurrency. It is best in class and also offers a lot of choice (which some other popular languages like JS and Go are not providing).

When it comes to IDEs I do think immature would also be my choice. There is a lot of movement on this front so I have hopes this may change soon. My main points are: 7.10 is out for a while but most editor integrations have/had (until recently) some major issues with it. Also Stack is bocoming quite popular, yet most editor integrations are not Stack-aware. Finally the editor integrations are not much plug-and-play. As said, this is changing rapidly with some necessary fixes to GHC/cabal made and projects like stack-ide and ghci-ng.

> When it comes to IDEs I do think immature would also be my choice.

If you have not already logged any issues, can you please list the top few things that bugged you about Leksah here and I will make sure they get added to the issue tracker? Even if they are already there it will help us prioritise to know what your pain points were.

Thanks

> 2: Your section on IDEs does not consider Leksah. I've just come back to this after a long time on Eclipse and Atom, and its now a mature IDE specialized for Haskell. You might consider bumping Haskell to "mature" based on this.

On a recent thread on Reddit, the Leksah maintainer acknowledged that on some platform (I forget which), Leksah crashes in every session, and has a CPU-spinning bug.

> the Leksah maintainer acknowledged that on some platform (I forget which), Leksah crashes in every session

Only on exit, so it has not been a high priority to fix.

https://github.com/leksah/leksah/issues/130

> and has a CPU-spinning bug.

This was in version 0.15.1.0, 0.15.1.1 and 0.15.1.2. It was fixed in 0.15.1.3 (released a month after 0.15.1.0).

https://github.com/leksah/leksah/issues/149

Please try Leksah! It is not perfect, but any feedback you could give would help us make it better.

Great to hear that Leksah is coming along. I'm a happy emacs user, but I think a good IDE environment can only help adoption.

Reply on news.ycombinator.com