12 ms·
Why I Use Elm in 2023
- iwanttocomment 3y agoAww, I was hoping this was about the email client.
- jmclnx 3y agoSame here, I had not heard of anyone using elm these days. I have seen similar titles for old software bouncing around, one example is ical, the tck/tk calendar application I use to use. I keep running across ical and my first thought is always "is ical still under development ?". At the time that was a very nice application and had potential. https://wiki.tcl-lang.org/page/ical https://wiki.tcl-lang.org/page/ical
- Rediscover 3y agoI loved elm(1). I stopped using elm (email) when I found mutt(1). Gads, that and procmail(1) were heaven. And when I finally intersected procmail with eliza, I was full of bliss... I was at AT&T (yes, THE AT&T) and it was hyper-satisfying that my co-workers recognized it and the marketing dept usually did not.
- foobarian 3y agoI stopped using elm when university upgraded to pine. But muscle memory was so powerful I have been aliasing my mail reader to elm ever since. :-)
- billpg 3y agoI was an embarrassing distance down the article before I realised they weren't talking about email. "Wow. I had no idea that email reader I used thirty years ago had such depth!"
- surprisetalk 3y agoYou might be interested in Himalaya, a modern email CLI. [1] https://github.com/soywod/himalaya https://github.com/soywod/himalaya
- dzogchen 3y agoIt's a shame Elm was abandoned. Impossible to justify for serious projects at this point.
- andrewstuart 3y agoIs elm dead?
- gregors 3y agoElm isn't dead the same way Yahoo isn't dead. It's around but it isn't gaining new traction, features, mindshare. I think it's a great language that people should explore for fun and learning. I think it was horribly mismanaged from a public relations perspective and at one point in time had a real shot at becoming a lot larger than where it will stay from now on.
- gekkostate 3y agoWould you mind sharing a link / citation for this? Elm releases are intentionally long and the project appears to be ongoing [1]. [1]: https://iselmdead.info/ https://iselmdead.info/ Edit: moved the position of the citation.
- dzogchen 3y agoThey can proclaim Elm not dead all they want, but if you take a look at the main repo the last commit was over two years ago, and it was to set up an auto reply to PRs that they probably would not get a response.
- G4BB3R 3y agoHe works on private branches to avoid speculation and pressure. Example, he gave this presentation yesterday: https://gotoaarhus.com/2023/sessions/2529/elm-on-the-backend https://gotoaarhus.com/2023/sessions/2529/elm-on-the-backend
- solatic 3y ago
- cpursley 3y agoWhat I loved most about Elm was the syntax, types and it's incredible CLI . But I found the architecture and working with foreign data (JSON APIs) just too strict to be productive.
- hombre_fatal 3y agoOn the other hand, I love Elm's decoder combinators so much that I miss it in every other language.
- jcparkyn 3y agoI like them in principle, but they really get annoying for objects with lots of fields (since the order has to exactly match the constructor), or for objects that need to round-trip (because there's twice as much code to write, and no way to verify that they're equal).
- revskill 3y agoWait until you want to support an enterprise customer and you need to adapt their requirements in a quick way. Elm is fine for learning, but that's all for me. Serious products for serious customers require more than "beautiful typings"
- boxed 3y agoI wrote some Vue instead of Elm because I was frustrated. But the more I work with Vue the more I am absolutely terrified of using it for non-internal web apps. Elm has some super annoying problems, like their disdain for nested structures or components, but I just don't know of anything better...
- ilrwbwrkhv 3y agoImba is the answer
- G4BB3R 3y agoVendr (1B+), NoRedInk and Humio are huge companies and their entire frontend is in Elm.
- 1-more 3y agoWhat's your working experience with Elm?
- cies 3y ago> Wait until you want to support an enterprise customer and you need to adapt their requirements in a quick way. Is that within Evan's ambition? I personally do not mind to use software that does not cater for enterprise in production at our small "enterprise" :)
- hombre_fatal 3y agoI still use Elm daily. Even if development on it is essentially paused for the foreseeable future, it is still much better than the alternatives for me. For example, all Elm apps having the same architecture ("TEA") is one of the biggest wins over alternative apps where every project, even those you make yourself, will do things differently. Elm Janitor (https://github.com/elm-janitor/apply-patches https://github.com/elm-janitor/apply-patches) is a curation and applicator of community patches to Elm proper. Haven't used it, but it seems like a promising way forward.
- awestroke 3y ago> Languages like Go and Elm spurn extravagance. They resist overcomplication. They force me to solve real problems instead of fighting compiler errors and stylistic differences. I hate this mindset. "<my favorite language> is used to solve REAL problems, other languages are not as good for creating VALUE. Any powerful language features, ergonomic syntactical sugar or tooling that does not exist in <my favorite language> is useless". So strange
- Frost1x 3y agoIt's a valid assessment depending on the context. There's a lot of software scaffolding that exists in places that, usually for good intentions, creates complexity in the hope of simplify the problem at hand. Sometimes it works, sometimes it doesn't. When it works, it's great. When it doesn't work, it adds yet another layer of complexity to deal with whatever problem you're trying to actually tackle. Ultimately it comes down to trying to do a cost/benefit analysis of the complexity at hand and deciding if the additional layers add enough value and how far your problem deviates from the supporting structures. The issue is, it's often quite difficult to know a priori what is helpful and what just adds complexity because goals are often moving targets and you have to try and assess the range of potential goals with the flexibility of all the middle layers you introduce.
- hombre_fatal 3y agoI think you're just reading it as "Elm/Go good, $yourFavLang bad". Maybe this makes more sense: Coming from more expressive languages, one of the good things I could say about Go's developer UX is that you are so helpless to circlejerk over abstractions that there is simply nothing else to do than to write concrete code to solve the problem. Elm is similar versus the huge type expressive power of Haskell. Elm's type system is so minimal compared to similar languages that you can't spend hours perfecting your higher kinded advanced type abstraction that perfectly annotates and cordons off the problem domain because there isn't enough typing power to do that. You have to go "welp, good enough" and move on.
- otabdeveloper4 3y ago> nothing else to do than to write concrete code to solve the problem And by that you mean "invent ad-hoc code generators instead of using built-in language features from the 21st century", right?
- cranium 3y agoI loved Elm as soon as I had a running app that I could refactor and be (reasonably) sure it would work once the compiler was satisfied. However, I don't like the way the project is run. It's one Benevolent Dictator that has a particular vision for Elm and he's not really sharing with the community. For context, the latest Elm version (0.19.1) was released in October 2019. It kind of feels like a nice tree house left to the elements because the person grew out of interest, but kept a lock on the door.
- G4BB3R 3y agoIndeed the releases are less frequent and Evan works in batches to avoid breaking changes every year. But he didn't left, he still works on private branches and on security patches when needed. Yesterday he gave this presentation: https://gotoaarhus.com/2023/sessions/2529/elm-on-the-backend https://gotoaarhus.com/2023/sessions/2529/elm-on-the-backend
- lolinder 3y agoWhy has his work not turned into a public bug fix update in 2.5 years? This feels a lot like Patrick Rothfuss on his Kingkiller Chronicles. The creator has a fan base he doesn't want to disappoint and who will defend his honor as long as he can give them any evidence he's actually making progress, but all the evidence suggests he's actually lost interest or doesn't know where to go from here. Not that there's anything wrong with losing interest in a hobby project. The problem with Elm is that it was pitched as more than a hobby project but then held so close to Evan's chest that no one else has been able to take over now that he's not maintaining it.
- SantalBlush 3y agoToo many people are concerned with the language's creator, how much he is working on, how many people love or hate him, what his motives are, what he wrote in a comment four years ago, and what he had for breakfast this morning. These comments are always the same: "Elm is great, but..." Then they dig up some drama about its creator with a years-old post. If the language is great, then maybe they should use it and stop fretting about the person who made it.
- GiorgioG 3y agoIf you want to use Elm for your hobby project, go for it. Everyone else, choose something that has a well established development team - the operative word being team. One-man development efforts (no matter their genius/brilliance) are too risky to depend on for serious work that needs to work/be-supported in 5+ years.
- giraffe_lady 3y agoI was also using it for these reasons up to about 10 months ago. I've switched to rescript now because it still addresses most of these, while being a lot closer to the mainstream of frontend programming. Rescript does piggyback on normal JS ecosystem and build systems so comes out worse there. But it's easier to integrate with existing js codebases and npm packages for the same reason, and its output can be used from js in any framework if you plan for it. I was really missing the elm command/update model for a while but at some point I realized adding that semantics to a react reducer with a custom hook was completely reasonable, and there are a couple existing projects doing exactly that. I wrote my own in an afternoon and have been copying it around to new projects since. I'm like 90% happy with this transition now. It doesn't always feel quite as safe & magical as elm did, but it's also a lot easier to integrate with other systems.
- ronanyeah 3y agoInteresting, got any repos written in this style?
- giraffe_lady 3y agoNot that I can share unfortunately. But here is the implementation I got the idea from. https://github.com/mjal/rescript-use-tea/blob/master/src/UseTea.res https://github.com/mjal/rescript-use-tea/blob/master/src/Use... I defined the actions a little differently and followed the rescript-react pattern of having effects return an Option of a cleanup fn but most of the idea is there. Looking around just now I also found this PoC of someone doing a very similar thing but all inline with react. https://github.com/mishaszu/rescript-model-view-poc/tree/main https://github.com/mishaszu/rescript-model-view-poc/tree/mai... Really the only jump you need from react to the elm architecture is having the reducer be (State, Action) -> ('State, Effects) instead of simply returning the new state alone. The then you have a useEffect that invokes the side effect fns, passing in dispatch so they can send updates back to the reducer & so reducer stays pure. There are a bunch of different ways to set that up, and honestly a lot of react apps blunder into an accidental and incomplete version of this anyway it's such a natural model.
- kkfdkerpoe 3y agoElm has lots of great ideas, but if I were making decisions in a company, I wouldn't use it in production for anything big and long-living. Simply too much of a risk in terms of support, and finding developers with experience using it. Only contacts I've had about Elm positions have been about rewriting existing Elm apps to something else.
- truculent 3y agoAs a counterpoint to the inevitable "Is Elm dead?"[0] comments, how many other languages are still rock solid after 3+ years without a new version? Shouldn't we aspire towards using tools that are stable because they are complete? What is the maintenance burden of the average React app? When I have written an Elm app, I feel confident that I could come back to it in a few years time with no issues. To me, this stability is a testament to the language's thoughtful design and rejection of the constant churn of contemporary web development. At the risk of sounding like a Game of Thrones fan waiting for Winds of Winter, I look forward to the next version coming out with modest changes and bug fixes whenever it is ready. [0]: https://iselmdead.info https://iselmdead.info
- hu3 3y agoLooking at the number of opened bugs and lack of releases, I wouldn't call it rock solid. https://github.com/elm/compiler/issues https://github.com/elm/compiler/issues
- lolinder 3y agoOuch, not just the number, look at the type of issues. "Compiler error...", "compiler panic...", "elm publish hangs indefinitely..." They never made it to 1.0, so it's not surprising, but major compiler bugs coupled with no chance of a patch (2.5 years since the last bug fix update) definitely suggests the language shouldn't be used in large projects.
- mjaniczek 3y agoCan you please list which of these compiler bugs are _major_? There was a commonly encountered compiler bug in 0.19.0 (Map.! crash) and the 0.19.1 version was the result of fixing that. During 4 years of writing Elm full-time (close to 500kloc total) I have encountered only a "rank 2 typevar" typechecking bug _once_ and it was easy enough to work around. The Elm code that large projects need doesn't really trigger compiler bugs and crashes of the kind you'd see in the GitHub Issues. If GCC has some bug reports open about crashes, but your code doesn't really trigger those in practice, would you call GCC unsuited for large projects?
- cies 3y agoWe also use Elm in 2023, just got the first project to production a few months ago and we absolutely love it. Finally a way to tame the complexity of browser-run-code. We only use it when there is complexity: when there is just a little progressive enhancement needed on a SSR HTML page we happily use vanilla JS or jQuery (we're looking for a good TS-based jQuery-like solution the fits that bill). What we like about Elm: * makes us think about tech design issues early on (you cannot just ignore them) * its a transformative experience: devs become better at writing any language after having solid Elm experience * its fast to compile compared to TS+React+Redux+Babel+WebPack+... * no unhandled runtime errors! (yes it is true, no more errors with Elm) Just like I find Ruby a very nice language that was hidden in Perl, I see Elm as a very nice language that was hidden in Haskell. Thanks Evan for creating it. And yes I truly believe Elm is not dead but merely finished to a great extend. Oh, as a bonus, want to have your mind blown, check out this: https://www.youtube.com/watch?v=nSrucNcwlA8&t=275s https://www.youtube.com/watch?v=nSrucNcwlA8&t=275s (when I watch that video I cannot unhear "look at all the boiler plate im not writing" in David Heinemeier Hanson's high pitch voice; referring to the original Ruby on Rails demo)
- the_gastropod 3y ago> no unhandled runtime errors! (yes it is true, no more errors with Elm) I used to work with elm some years ago and my coworkers claimed this as part of their reasoning for choosing elm. Shockingly, we still had runtime errors! Elm helps reduce some type system based runtime errors. But that’s only a subset of exceptions, and it’s not perfect at even catching those. Try this in elm: div [ attribute "@style" "color: green" ] It’ll compile just fine. And crash completely at runtime.
- cies 3y agoWow, it indeed crashes at startup (a very reasonable place to "crash" when you avoid all safety mechanisms and put an @ in an HTML attribute key). There are some fully type safe CSS systems in Elm, but they are 3rd party libs.
- ilrwbwrkhv 3y agoLamdera is closed source and you deploy on their system. It has been forgotten already. Rails is thriving, open source and a beast. I think that is the problem with the Elm community. They are too uptight to do open source properly. They need to listen to some Humble from Kendrick Lamar.
- alberth 3y agoThe contrarian HN view is below. 432 comments | 3-years ago https://news.ycombinator.com/item?id=22821447 https://news.ycombinator.com/item?id=22821447
- HissingMachine 3y agoThe fact that Elm had traction and popular support (books/youtube tutorials/etc) most language or framework projects would kill for and then basically dropped is almost criminal in my mind.
- fnord77 3y agoI thought this was going to be about the Elm email client. I guess I'm old af I don't think I'd ever use "elegant" to describe Go it's a workhorse language that's readable and full of utility. When I think elegant, I think Clojure. Not that I'd want to use it day to day (I have)
- drewg123 3y agoI thought this was going to be about the Elm email client. I guess I'm old af You are not alone. I do kernel programming in C. I've seen so many languages come and go since the 90s that I can't keep track of them all. I never used elm the email client (I was more of an emacs rmail person at the time).
- NikkiA 3y agoMy initial reaction was 'Not even pine? That's hardcore.' Then realised it probably meant the programming language
- nymalt 3y agore famous Elm error messages. This one I got when I was learning Elm 4-5 years ago. Elm uses a different name for the “not equal” operator: 5| text "Hello!" != "balbla" ^^ Switch to (/=) instead. Note: Our (/=) operator is supposed to look like a real “not equal” sign (≠). I hope that history will remember (!=) as a weird and temporary choice. Wondering if it is just me, or it really is passive-aggressive? It was the first red flag for me. upd: formatting
- 3836293648 3y agoThe note absolutely is, the use of `/=` is just consistent with Haskell though, which to me makes perfect sense.
- spokeonawheel 3y agoits fairly direct. And not wrong. Passive aggressive might be like this "there are some languages that feel the need to use !=. They have the 'opinion' that this was a good idea, look at them. They are so cute trying to be a real language with such *interesting* design choices"
- thekogmo 3y ago[flagged]
- ARandomerDude 3y agoWhat is that? He must have died while typing it. Oh, come on! That's what it says. Look, if he was dying, he wouldn't bother to type "to write a post like this". He'd just say it. That's what's typed into the form. Perhaps he was dictating it. Oh, shut up! Does it say anything else? No. Just "to write a post like this."
- gv83 3y agoelm seems to be a very opaque project; caution must be taken before adoption. the architectural model is good, and there are many projects mimicking it in a more open way.
- Ylmaz 3y agoDo you know of an up to date Elm course?
- vcryan 3y agoSometimes I dream about writing my own secret coding language that no one else knows so I can have this personal/private connection to the digital products I build. I would make all my code open source, but no one would understand it. But that would take a lot of effort, so I just use Elm instead.
- retepna 3y agoI can relate to most points in the article but definitely not #4. I'm a newbie and Elm's ways of declaring types are confusing to me. There are custom types, type aliases, records, extensible records, opaque types, phantom types, wrapper types [1]. However, I still wasn't [2] able to model a list of items with a common base type without having to switch-case through all possible types. [1]: https://gist.github.com/JoelQ/6b303d9ad450537163b6f8f6cf8a4ed8 https://gist.github.com/JoelQ/6b303d9ad450537163b6f8f6cf8a4e... [2]: https://ellie-app.com/mQ52TY6k3zZa1 https://ellie-app.com/mQ52TY6k3zZa1
- hombre_fatal 3y agoI don't work much with extensible records myself, but maybe an easier solution is to invert it so the item variants are contained in a field: type Item = { name: String, year: Int, kind: Kind } type Kind = Cd { artist: String } | Book { author: String } | Shoes { size: Float } https://ellie-app.com/mSVCN8dQqX8a1 https://ellie-app.com/mSVCN8dQqX8a1 Consider joining the Slack community: https://elmlang.slack.com https://elmlang.slack.com -- The #beginners channel is a great place to ask these kinds of questions.
- retepna 3y agoThank you, that's indeed a better way to model it!
- terminatornet 3y agohighly recommend the talks "making impossible states impossible" and "make data structures" by richard feldman. https://www.youtube.com/watch?v=IcgmSRJHu_8 https://www.youtube.com/watch?v=IcgmSRJHu_8 https://www.youtube.com/watch?v=x1FU3e0sT1I https://www.youtube.com/watch?v=x1FU3e0sT1I the talks are geared towards elm but I think they offer some great advice applicable to programming in general.
- deathtrader666 3y agoHas the Elm community finalised a canonical way to work with Elixir Phoenix?