You may find it distracts from whatever technical point you were trying to make.
It's absolutely hilarious how Elm of all things was the #1 enemy of HN the last couple days. A language just about nobody uses (except me).
Yet suddenly everyone is just three degrees away from someone else who was irreparably wronged by Elm's creator. People coming out of the woodwork to show that they, too, are offended by such reprehensible behavior like removing a couple features from a programming language.
Web developers are literally the most oppressed people on the planet. This Evan guy messed with the wrong motherfuckers!
It's a great language. The community has been nothing but stellar to me - a complete novice at not just FP, but also JS and web in general.
The entitlement is unreal. "How DARE you create this great free thing, and have the AUDACITY to make it work the way you want it to?!"
Someone’s always going to get bent out of shape (<— I expect I’m creating a demonstration of that right here) with language usage, but please don’t write like a computer when talking with humans so as to avoid these sorts of remarks.
It’s kind of like interrupting someone when they are trying to make a point that is important to them by saying, “hey, you’re having a bad hair day” and then acting like this shouldn’t impact the confidence they have in their point.
In that case, why not use typescript for everything? Being pure is nice and all but it's not a goal in itself, especially if the language is extremely limited as a result.
Anything port talks to is NOT Elm. Any custom element is also NOT elm. I really like some smart people in Elm community, they are kind. But I think they are like 3% of all. The real problem is development process and communication.
Agreed. It's a non-open-access open source project.
I've quickly learned that I much more enjoy scrapping redundant code and relying even more on the type system, with things like Higher-kinded types, GADTs, etc.
Elm for me fills the niche of stepping stone into Pure FP (pure as in purity). It's a language I would be able to convince my coworkers to try out, and once they've gotten their feet wet, they can move onto PureScript or GHCJS.
The reason why stopping at Elm, IMHO, is bad, is that it does not foster innovation and trying out things, but restricts itself purely to the subset of what the core team has discovered/learned. This makes it impossible to try out new exciting things like this "A proof-of-concept UI library based on the incremental lambda calculus"[0] that does away with the need for VDOM diffing, and other interesting things.
Don't get me wrong, there is certainly appeal to having a simple language that everyone can quickly master (like Go), but it isn't the be all end all.
It's kind of like how Java and Go are shitty when all you want to do is masturbate over clever solutions, but there's something to appreciate about them for that same reason.