Just to play devil's advocate for a moment; Despite my suggestion, and as much as I'm an advocate for package curation I don't think that it's the right first step towards solving the problem.
In my opinion the realistic solution is one that may already have been discussed in the past: 1. Allow publishing any package, except prevent publishing packages that *depend* on packages that could cause run-time exceptions. 2. Issue a warning when you try to install a package with native code / effects. Censoring packages indirectly based on dependencies sounds like a cop-out at first, which is why I think people haven't taken it seriously. But I think people haven't considered it as carefully as they should. Breaking it down based how this affects each of the three concerns: * Evan and other people with that take the "long-view" want to prevent run-time errors from becoming endemic to the ecosystem. No transitive dependencies means that run-time errors can be traced to a function call you made directly in your app. * From a marketing perspective we don't want to water down the "no run-time errors" argument. Issuing a warning on installation provides some justification. Consider that clumsy JS interop negatively affects user acquisition and - perhaps more concerning - on user retention. * Existing users and commercial users want to be productive. Being productive in the short term is as important as being productive in the long term when you have limited resources. P.S. What attracted me to Elm was that it was being developed in a similar way to how a startup develops a product rather than how an academic might. However, I'm increasingly concerned that the current course that is set for Elm may be more dogmatic than it is pragmatic. It worries a great deal that Elm's development methodology is based on early Python history. The world moves far more quickly than it did in the 90's and I think it's dangerously complacent to imagine that we're still living in the same era. Consider that SourceForge was launched in 1999, 8 years after Python first appeared. It's hard to hear but the world just doesn't work the same way anymore; people aren't working out of their basements in isolation (though they may be working out of their basement in a well managed team). -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
