Elm doesn't seem to use semver (which requires that "A normal version number MUST take the form X.Y.Z")
Clearly the internal API existed because Evan et al. decided they needed to use it. So why did they decide it a feature that was so obviously necessary was too complicated for the hoi polloi?
I asked upthread about native versus ports and somebody was kind enough to mention ports were async only.
But I'm still curious about exactly what people were using native for and why at least some users don't feel they can rewrite easily - care to share what you used and why, and what your thoughts are about replacing it?
(the discussion around this has, so far as I've been able to see, devoid of concrete examples, and now the question's nerd sniped me :)
Native's existence was an implementation detail. no one using it didn't know it was likely to go away if they read anything about it from core. it was undocumented, but where you could find any documentation it said very clearly not to use it. people used it anyway. I was one. but I knew going in that it would likely disappear.
> why was the version number then a minor increase (at least according to commonly accepted understanding, i.e. semver) and not a 0.20 or whatever else, especially if there are breaking API changes.
https://semver.org/#spec-item-4
you not understanding semver doesn't make elm bad