why do these elm hit pieces keep getting dug up and reposted? It's almost always in response to some other elm post (there was one yesterday). People use elm in production at quite a few companies without worrying too much about the concerns laid out in the article, but it feels like people seem almost fervent in their need to justify their reason for leaving elm and why other people shouldn't use elm.
Why I'm Leaving Elm (2020)
31–40 of 61 posts
Re: Why I'm Leaving Elm (2020)
#32Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old. I liked Elm before, and was a great fit for internal corporate applications. Something like an admin control panel or a monitoring tool. Are there any similar projects that are in the "more alive" state?
I dislike the constant churn of React and other libraries, that often add change for change's sake, and break backwards compatibility or depend on too many libraries. At the same time Elm is maybe too much in the other direction.
Re: Why I'm Leaving Elm (2020)
#33previously: https://news.ycombinator.com/item?id=22821447 (April 9, 2020 — 732 points, 431 comments) I was surprised this is only the first reposting—I thought for sure I had seen it more often than that.
There is a small group dedicated to ensuring nobody uses a language that, according to them, nobody uses.
*Edit: https://news.ycombinator.com/item?id=34750499
https://news.ycombinator.com/item?id=35499892
https://news.ycombinator.com/item?id=34748430
https://news.ycombinator.com/item?id=34747958
https://news.ycombinator.com/item?id=34747376
https://news.ycombinator.com/item?id=31666100
https://news.ycombinator.com/item?id=30035052
https://news.ycombinator.com/item?id=29308496
https://news.ycombinator.com/item?id=28499112
https://news.ycombinator.com/item?id=27823758
https://news.ycombinator.com/item?id=27819792
https://news.ycombinator.com/item?id=26862280
https://news.ycombinator.com/item?id=24334514
Re: Why I'm Leaving Elm (2020)
#34Take a look at F# and Fable (F# to JS compiler)
Re: Why I'm Leaving Elm (2020)
#35Ah, another “why I’m leaving X” post, I’ve never seen these kinds of posts as particularly fruitful regardless of the language they go on about. Engineers can assess the pros and cons of a technology for themselves based on their needs, and usually these kinds of posts don’t have the relevance their authors wish they would. I think they serve more as emotional catharsis (or worse) than actually meaningful content (mo…
Reasons you might want to not use Elm:
Great. These are only technical reasons, though. What’s the community like? What’s the process like if you want to contribute to the core project?
Oh, discussing that topic is verboten. It would be too cathartic.
Re: Why I'm Leaving Elm (2020)
#36Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old. I liked Elm before, and was a great fit for internal corporate applications. Something like an admin control panel or a monitoring tool. Are there any similar projects that are in the "more alive" state?
Re: Why I'm Leaving Elm (2020)
#37Earlier quoted context omitted.
HN can’t resist crapping on Elm and Tailwind. I wonder what the other popular hate topics are?
Tailwind? I must've missed that; I thought HN liked Tailwind for the most part.
Re: Why I'm Leaving Elm (2020)
#38Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old. I liked Elm before, and was a great fit for internal corporate applications. Something like an admin control panel or a monitoring tool. Are there any similar projects that are in the "more alive" state?
Elm is pretty much finished (meaning feature-complete) IMO. Not much needs to be changed. I love Elm. I can always go back to a project and get back on it in 2 minutes. The compiler is superb. The problem is one must roll on their own almost everything. I dislike the constant churn of React and other libraries, that often add change for change's sake, and break backwards compatibility or depend on too many libraries.…
Re: Why I'm Leaving Elm (2020)
#39[flagged]
No debts are left on either side.
But they should (according to you) have “stayed away from OS”? Why?
They did things and then they stopped. They didn’t owe anyone to begin with, and they don’t owe anyone now.
And yet they should have “stayed away”?
This absolutist “no one owes anyone” gets hypocritical really fast when you at the same time try to judge someone for doing, well, basically anything. Because they don’t owe you are anyone else anything (by your own logic).
So how can you possible judge them?
Re: Why I'm Leaving Elm (2020)
#40Elm is pretty much dead at this point. The last substantial commits in the Elm repositories are about 2 years old. I liked Elm before, and was a great fit for internal corporate applications. Something like an admin control panel or a monitoring tool. Are there any similar projects that are in the "more alive" state?
Elm is pretty much finished (meaning feature-complete) IMO. Not much needs to be changed. I love Elm. I can always go back to a project and get back on it in 2 minutes. The compiler is superb. The problem is one must roll on their own almost everything. I dislike the constant churn of React and other libraries, that often add change for change's sake, and break backwards compatibility or depend on too many libraries.…