3 ms·

Who cares? It’s a computer program, just have it do what purpose you require

• macintux 5y ago
  Forking has long-term maintenance costs, even without the hassle of trying to hide your efforts from the Elm maintainers. I’d be fine forking it to pursue a personal project. I’d never do that for any critical business need.
  • jeofken 5y ago
    • Your company has a patch allowing installing binary code from other sources • When you want to update to a new version of Elm, do git rebase and reapply the patch. • Now your source tree and history is identical to upstream, plus one commit Most likely the code restricting installing binaries from only one source isn’t changing a lot, so patch conflicts should not be too much of a hinderance