Regarding the pain of wiring up a subscription port, have you seen Task.perform <http://package.elm-lang.org/packages/elm-lang/core/latest/Task#perform>? It allows you to do async work using no ports other than The Elm Architecture itself.
As for doing pure but computationally intensive work in a Task, you can do it in Elm: Task.succeed () |> Task.andThen \_ -> do hard stuff This won't work for inner render loops, and the asynchronous Elm will still be slower than JS, but it may be useful in some circumstances. -- 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.
