3 ms·

Terrible backwards compatibility. No escape hatches: The only one who is allowed to do bindings to Javascript is the maintainer. No typeclass mechanism or sim

• carapace 7y ago
  Thanks for replying. :-) > Terrible backwards compatibility. At version 0.19... > No escape hatches: The only one who is allowed to do bindings to Javascript is the maintainer. I trust Evan Czaplicki. Did you read his thesis[1]? M'boy can think. > No typeclass mechanism or similar. Okay, but then my question becomes what business value are you unable to realize without a typeclass mechanism? In other words, what is the vital use-case or feature that is so much easier to implement with a typeclass (relative to some other, less elegant solution) and that is so valuable that it counter-balances or outweighs all the benefits of using Elm? (Same question applies to JS escape hatches. And, in theory, if the payoff was high enough you could fork Elm and patch it to do what you needed.) [1] "Elm: Concurrent FRP for Functional GUIs" https://www.seas.harvard.edu/sites/default/files/files/archived/Czaplicki.pdf https://www.seas.harvard.edu/sites/default/files/files/archi...