News for hackers. Stuff that matters.
Re:Why I Use Elm in 2023 by surprisetalk on Tuesday May 23, 2023 @08:58AM (#36043594)
Author here :)

I definitely don't think ergonomics and features from other languages are useless! I just feel a bit overwhelmed and distracted by variety sometimes, especially when working on teams.

For example, about 50% of the JS teams I've worked with collectively agreed not to create new classes. I think I'd prefer working with JS if there were only one way to do things, but it doesn't mean that classes are bad or useless.

Re:Why I Use Elm in 2023 by eweise on Tuesday May 23, 2023 @11:22AM (#36045615)
I like Elm but there are some things that would make life easier and not add much cognitive overhead, like updating nested records for instance. The current syntax wouldn't even need to change.
Re:Why I Use Elm in 2023 by Skeime on Wednesday May 24, 2023 @02:47AM (#36054883)
It’s even worse as you cannot even update a record if it has a qualified name.

    { Module.record | field = value }
is not allowed. So either, you need to import record unqualified, or you need a let construction.

I somewhat get the restriction on nested updates (though I don’t agree with it), but I absolutely do not understand this.