News for hackers. Stuff that matters.
Re:Small Assets without the Headache in Elm 0.19 by chosenbreed on Tuesday August 21, 2018 @10:28AM (#17809892)
> Additionally I'm glad .19 finally came out. But 18 months was really long. On the basis that nothing was actually broken 18 months is not that long. I think there are benefits to be derived from working with a language/platform/ecosystem that doesn't change every few weeks. Just think about how many changes Angular has had in that time...
Re:Small Assets without the Headache in Elm 0.19 by kylecordes on Tuesday August 21, 2018 @11:37AM (#17810538)
Although many people have seared-in memories about the transition from AngularJS 1.x to Angular 2.0, since 2.0 the improvements and Angular have a lot in common with today's Elm release. The same code still compiles, to smaller and faster output. The few breaking changes or deprecations happen slowly, with plenty of warning, and very little effort to keep up.

Of course it's more dramatic to find and discuss stark differences between "competing" platforms, but the boring truth here is that Angular and Elm are on the same side of the "should we be careful and methodical about development and change?" question.

Re:Small Assets without the Headache in Elm 0.19 by aarpmcgee on Tuesday August 21, 2018 @11:41AM (#17810584)
Not sure if "nothing was actually broken" is true... very few of the dependencies from my 0.18 project work with 0.19.
Re:Small Assets without the Headache in Elm 0.19 by Skinney on Tuesday August 21, 2018 @01:07PM (#17811495)
I think he was saying that during those 18 months of 0.19 development, everything was stable.

0.19 is very much a breaking change.