The Elm Architecture

Re:The Elm Architecture by throwaway237468 on Sunday August 26, 2018 @02:25PM (#17847124)

There are tons of bugs in 0.18 compiler and 0.18 libraries that will never be fixed. Many of those have / had pull requests by the community members open for more than a year but they were never merged. These are tiny fixes, not 200 lines of code adding a new feature. There's no way to fork a package and apply a patch in 0.19 if the package contains native code. All you can do is report the bug and hope Evan fixes it before your deadline (which ranges from 1 week to 3 years).

Edit: Using a throwaway so I don't get banned from Elm Discourse and /r/elm. I still have production applications using Elm.

[ Parent | on HN ]

Re:The Elm Architecture by jnbiche on Sunday August 26, 2018 @05:29PM (#17848029)

> There's no way to fork a package and apply a patch in 0.19 if the package contains native code.

Yeah, if for no other reason than this I would never use Elm for a production site. The entire reason for using open source for me is being in control of the code, and not having to depend on a third party for a fix if things get bad enough.

[ Parent | on HN ]

Re:The Elm Architecture by technion on Sunday August 26, 2018 @07:02PM (#17848409)

Can someone clarify this? I've seen several references to how only a certain team can write modules using certain code.

If someone else can do it, why can't you?

[ Parent | on HN ]

Re:The Elm Architecture by rtfeldman on Sunday August 26, 2018 @09:48PM (#17848943)

Here's the explanation: https://discourse.elm-lang.org/t/native-code-in-0-19/826

[ Parent | on HN ]

Re:The Elm Architecture by sridca on Sunday August 26, 2018 @06:01PM (#17848175)

> Edit: Using a throwaway so I don't get banned from Elm Discourse and /r/elm. I still have production applications using Elm.

It's pretty sad that you have to do this. Any community that has the effect of instilling such fear doesn't seem healthy to me.

[ Parent | on HN ]