Some people have been talking about the fact that not all
elm packages are fully updated to 0.19 yet. One example is
elm/websockets. I am working on that sort of thing now, but I want to explain the reasoning about why I am working on it after the release. I saw two paths here:
- Block 0.19 on those packages, making the release come out a couple months later. Based on posts like Is Evan Killing Elm’s Momentum? and nearly had a heart attack, no updates in 18+ months?, I was under the impression that folks would prefer some other path.
- Try to do the release earlier, leaving some packages for later. Most people can update to 0.19 and get the benefits, so their life is better. Some people some people may have to use ports or stick with 0.18 for a bit. Their life is either the same or better. This also gives me a chance to try to improve certain packages, perhaps finding a nice way to cover the Elixir folks who need certain features for their scenarios.
Given the data, I felt like choosing path (2) was a reasonable approach. In my experience with Haskell, I always wait to update to the latest compiler version because there are lots of authors with lots of packages. It takes a while for everything to get updated! We had a two month testing period with this release, so a decent number of packages were updated, but not everything. Not everyone follows that stuff super closely, and that is okay. I just wait a bit to updated my code.
I did not think to make a note about this because, to me, it did not seem like a mysterious decision, to me. It is very hard to anticipate all the ways people will see things a different way than you, especially when you have a big release with lots of stuff going on. So now you have that information.