News for hackers. Stuff that matters.
Re:State of Elm 2017 Results by PhineasRex on Friday July 28, 2017 @04:24PM (#14877264)
I've heard more than one person argue against automatically generated encoders/decoders since it's easy to accidentally introduce breaking changes to your API by renaming a record field / class method.

If that's your view then Elm's approach is a plus for the language since it eliminates a potential pitfall.

Re:State of Elm 2017 Results by codygman on Friday July 28, 2017 @07:34PM (#14878441)
> argue against automatically generated encoders/decoders since it's easy to accidentally introduce breaking changes to your API by renaming a record field / class method

Can anyone further substantiate this argument, I feel like it's not very strong as is.

Re:State of Elm 2017 Results by shakna on Friday July 28, 2017 @06:17PM (#14878042)
Haskell's way of pre-defining an interface handles that, with less than a quarter of the boilerplate.