Putting Down Elm
mkndrsn.com
Putting Down Elm
1–10 of 73 posts
Re: Putting Down Elm
#2This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
Re: Putting Down Elm
#3This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
Exactly what I wanted to ask. Can we mere developers have some context to it?
Re: Putting Down Elm
#4This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
I've used typed languages, and pure ones, but what I've found to be really special about Elm is that the compiler is super helpful. This also makes learning the language really enjoyable, as you've got someone helping you along. :)
Re: Putting Down Elm
#5This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
Exactly what I wanted to ask. Can we mere developers have some context to it?
Haven't used Elm myself, but I assume this argument is based in large part on the strength of the Elm compiler error messages. For example:
https://twitter.com/ID_AA_Carmack/status/735197548034412546
Re: Putting Down Elm
#6This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
Without having used Elm that much myself: One of its features is its very user friendly error messages. I imagine the author is comparing with more dynamically typed languages, where when you leave your work in the middle of something, there's usually a bit of digging when reopening it and continuing work, which he contrasts with Elm, where the compiler is quite excellent at reporting your unfinished work (in the form of helpful type errors), allowing you to quickly grasp at what point in your program you were at.
Re: Putting Down Elm
#7This has always been my experience with TDD, at least if you always leave yourself a failing test when you go. A lot more labor-intensive, since you are essentially writing the "compiler" as you go, but a similar effect.
Re: Putting Down Elm
#8What does this mean? There is almost no detail in this other than "Wow Elm is great and the compiler gives persistent, detailed messages"
which I think most people interested in Elm already knew.
Re: Putting Down Elm
#9This kind of comment about Elm is quite hard to understand without context. Have you ever used a typed language before? Have you ever used a pure language before? Is there something special about Elm that gives you this kind of benefit, or do other languages do the same thing?
Not the author but I've had similar experiences. I haven't used Haskell or OCaml in my day job (though I would like to if given the opportunity). I have written some trivial and slightly serious programs in both of these languages. I've even worked up a few small programs in Agda.
Elm, IMHO, is in a class of its own. There's a strong focus in the design of the language to be usable and friendly to the developer. The focus on structural typing, the error messages, and the tooling all go a long way to bring the developer from beginner to expert with as little friction as possible.
In contrast I find this is the biggest hurdle for Haskell and OCaml. It's simple enough in either language to get started but there's a steep learning curve to becoming productive and the tooling, documentation, and even the design of the prelude libraries are the largest stumbling blocks for transitioning from an intermediate developer to an advanced one.
update: grammar
Re: Putting Down Elm
#10What does this mean? There is almost no detail in this other than "Wow Elm is great and the compiler gives persistent, detailed messages" which I think most people interested in Elm already knew.
I guess the only new addition is that a side-effect of the very helpful errors is that it's easy to eventually come back to your work later on.
There's also a lot less state to keep in your head, as it's usually a lot more transparent.