Hacker News Reader

Comment by aeorgnoieang | Hacker News Reader

If releases are the primary means by which bug fixes are distributed then a slow release pace means a slow pace at which bugs are fixed.

Otherwise, I too enjoy the stability of using working tools that don't necessitate a lot of fast-paced changes.

View on HN

Agreed.

But the main thing to check first is : are there many bugs? Struggling to find any. On the other hand in js...

I suppose it's more of a perception thing. We are used in js-based projects to have a lot of bugs as a given, so plenty of updates is a good thing.

Yes, there are bugs in Elm. Anyone who's worked on a production app will have run into issues with the compiler and/or first-party libraries, all of which are maintained by one person (as well as all of the official documentation, the package repo, CLI tooling, etc, etc). I'm a big fan of Elm in general, but I couldn't recommend it to someone unequivocally.

No one claimed it's perfect and bug free. But let's compare it to any js stack with thousands of libraries in the project's `node_modules` directory, written by thousands different contributors. That's what Elm is replacing.

You did claim that you were “struggling to find any” bugs in Elm. There are definitely a lot of bugs in the JS ecosystem, but one should also compare the avenues for remediating bugs in that ecosystem versus Elm (easier to fork/patch buggy code, more frequent bugfixes, more alternatives, etc).

Reply on news.ycombinator.com