3 ms·
I've been using Elm on and off for projects for the last couple of years. I find that most of the complaints are just discomfort at how Elm isn't developed the
by crusso 9y ago
I've been using Elm on and off for projects for the last couple of years. I find that most of the complaints are just discomfort at how Elm isn't developed the way that many other projects are. It gets in people's heads that they have to trust in Evan's judgment when they don't see a new release popping out every quarter.
I actually like the pace of releases and lack of frequent breaking changes. I'll put some projects aside for 6 months here and there, then come back to them when I have time. Most rapidly-evolving frameworks require you to update all your libraries and fix a ton of breaking changes when you don't touch them for a few months (I'm looking at you, Swift). After I spend all that maintenance time, I often wonder at the value of those changes in the first place. Were they really changes that buy me new flexibility with the language? Or were things just renamed and shuffled around with syntax changes made for no great reason?
When talking to people about using Elm, I discourage them from using it if they're the kind to obsess over the release cycle of a framework that's stable today and that allows them to get quality work done.
- msangi 9y agoThis is a good point, but on the other hand it's sad too see that 0.18 has been abandoned and there are pull request that would fix bugs being ignored. I don't mind that 0.19 is taking long time to be released, what bothers me is that there are no bugfix release for 0.18
- smoe 9y agoI'm not using elm but i do like slower release cycles. For example some years ago I wanted to give node.js a shot for some backend stuff for a side project. But every couple of days when I wanted to work on it I had to spent half an hour fixing the build, so I gave up. But at least in the linked discussion, the pace of releases doesn't seem to be an issue, but the lack of communication about what is happening. No clarity whether native extensions will work, if pull requests opened years ago will be merged or at least responded to, whether there will be bug fix releases, etc. To me it seems, that elm community uses this straw man making it about people just wanting faster release cycles in response to valid criticisms in every unpleasant reddit thread I've have ever seen. Not pointing at you here, since you are not mentioning specific cases.
- kungfooguru 9y agoYou like having a fix open in a PR for 2 years and then learning that your work around for the fact that fixes don't get merged or released is going to be also blocked? Because that seems to be what is happening to the person who opened this reddit thread.
- rtfeldman 9y agoThere are other workarounds; the poster chose that one but didn't have to.