3 ms·
Evan wants to design Elm as thoughtfully as he can, and has been deliberately resisting community evolution. Eventually it will get too big and too useful, and
by embwbam 10y ago
Evan wants to design Elm as thoughtfully as he can, and has been deliberately resisting community evolution. Eventually it will get too big and too useful, and he'll lose the ability to make big breaking changes easily. So he's tried to maintain control of the direction of the language and community during these early years while he figures it out. He's trying to reduce the feedback loop and come up with the best possible base before it starts to scale.
It feels like it's stabilizing. I expect that over the next year or so this will change dramatically and it will become much more community driven.
- dominotw 10y ago' during these early years' should feature prominently in their docs/website if that is case. If you go to http://elm-lang.org/ http://elm-lang.org/ they make it looks like its production ready. No mention of breaking changes/beta ect. You have to choose one or the other .
- GavinMcG 10y agoThe version number starting with a zero really ought to denote that, notwithstanding the JS crowd's seemingly fast and loose approach.
- t1amat 10y agoThe Elm community is very strict about semver. Given this context, in Evan's defense, the 0.17 version is not a mistake as the API is still in flux.
- methehack 10y agoIt seems like communicating this approach to the community might be helpful for some. The poster's perspective is not unique (see the links in this thread). An evolution from benevolent dictatorship to democracy has advantages and precedent. Communicating with the community these intentions is important and a sign of respect and maturity. I think in itself it would be stabilizing.
- cpdean 10y agofor what it's worth, the compiler helps you find those breaking changes pretty quickly. much better than having bugs sneak up on you in production