Of course there are no guarantees, but 0.17 simplified a bunch of things and crossed off many of the goals Evan had for a stable release. I wouldn't be surprised if 0.17 stays around for longer than any previous release and he starts thinking about 1.0.
On Wed, May 25, 2016 at 9:05 AM, John Orford <[email protected]> wrote: > "0.17 is a good time to board the Elm train. :)" > > Because 0.18 won't break things massively again? Sorry! That was supposed > to be a joke, not snark. Couldn't resist. > > Luckily I am not badly affected > > On Wed, 25 May 2016 at 08:36 Peter Damoc <[email protected]> wrote: > >> Hi Mark, >> >> Elm is in development and minor releases can still break things in a big >> way. >> This is what happened with the switch from 0.16 to 0.17. >> This release got rid of Signals which have been with Elm since its >> conception. >> >> Lua's development is in a different stage where you can do minor releases >> without big changes and you can still use most of the old code unchanged. >> >> I empathize with the sensation of someone puling the rug from under you >> and, having gone through several porting sessions I can tell you that it >> looks worst than it actually is. >> I'm grateful for the changes made with 0.17 and I personally believe that >> something of this magnitude will never happen again in Elm. >> >> Keeping 0.16 available risks delaying further development because >> resources would have to be split and allocated to maintaining that branch. >> Elm is way too young to afford that kind of split. >> >> That being said, the guide is getting better every day, Evan's tutorials >> <https://github.com/evancz/elm-architecture-tutorial> already describe a >> lot of the functionality in the new paradigm and tutorials/examples from >> other people keep popping up. >> >> 0.17 is a good time to board the Elm train. :) >> >> >> >> On Tue, May 24, 2016 at 7:26 PM, Mark Hamburg <[email protected]> >> wrote: >> >>> I was talking with coworkers about my team's experiments with Elm and I >>> found myself having to blunt their interest because of the current state of >>> Elm 0.17 — documentation still has holes, tutorials haven't had a chance to >>> arise, some functionality is still missing relative to 0.16, etc. This >>> wouldn't have been a problem in some other languages I've advocated for in >>> the past — e.g., Lua — because I could have said "Elm 0.17 is out and it >>> looks like a big step forward. However, some pieces are missing and there >>> isn't a lot of material about it yet, so depending on what you want to do, >>> you may find it easier right now to start with 0.16 while the community >>> transitions." Except I can't really say that because access to 0.16 has >>> become much harder. For example, one can no longer just go to the web site >>> and browse the documentation for 0.16. (Or if one can, it's pretty buried.) >>> Contrast this with Lua where the 5.1 (released in 2006) reference manual is >>> available at online at lua.org and older versions are available as >>> archives. This leaves me with a problem when it comes to advocating for Elm >>> and when I explain the situation to people their response is along the >>> lines of suggesting that the Elm community can't be trusted not to pull the >>> rug out from under one. >>> >>> So, while I'm mostly interested in seeing 0.17 get fleshed out, I think >>> having a link on the front page of elm-lang.org that would take one >>> back to the 0.16 world would be a good thing while 0.17 matures. >>> >>> Mark >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Elm Discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> There is NO FATE, we are the creators. >> blog: http://damoc.ro/ >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Elm Discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Elm Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
