3 ms·
Elm has been around for a long time and yet it's still pre 1.0. AFAIK there hasn't been, and still isn't, a promise that what you write has any sort of forward-
by frou_dh 7y ago
Elm has been around for a long time and yet it's still pre 1.0. AFAIK there hasn't been, and still isn't, a promise that what you write has any sort of forward-compatibility with the next 0.x release.
On that note, it's interesting that publishers have already put out print books.
- G4BB3R 7y agoIt is just a number, react-native is not 1.0 too and it's is used in production world wide
- frou_dh 7y agoIf it was just an arbitrary number then I wouldn't have been able to write the rest of my comment. Elm has history of adopters being surprised by the hammer coming down.
- Grimm1 7y agohttps://semver.org/ https://semver.org/ 'If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.' To a significant part of the community 1.0 means a stable API with considerations of backwards compatibility. I know many people aren't using pure semver but the implications of a 1.0 have in my opinion extended beyond that point and beyond semver in general.