On Tuesday, November 8, 2016 at 2:45:26 AM UTC+11, Ian Dickinson wrote: > > >> With respect, I'm not sure that the essence of JS fatigue is new features > of the language itself, although I suppose ES5 to ES2015 is quite a big > change. As I hear it, it's rather the explosion of build tools, library > managers, static analysers, code architectures, front-end frameworks and > Alt-JS syntaxes that compile to JS. Too many choices, that keep changing > too fast! If you're convinced by Elm, then sure, it's the answer to a lot > of those choices. But if you're still at the point of making that choice, > Elm just adds one more set of options to most of those categories, and - > from one perspective - adds to JS fatigue. >
I think JS Fatigue is not much a matter of "too many options" but rather a problem of "wiring all that stuff up", and having to rewire everything again the next time you want to change one of the basic libraries. I really liked coding in Elm even when I was struggling with the language itself, because I didn't have to think about all of that wiring stuff. It felt a much closer experience to coding in, say, python or even node, which have definitely too many libraries with overlapping scopes, but do not suffer (too badly) of a "wiring things together" problem. -- 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.
