Yeah I think that could be a great middle ground (keeping around all of the previous js plumbing that wires up the big libraries and newer platform APIs and then exposing js methods to interact with these bits through the elm ports). My main hesitation there is that the core react & redux components and state management haven't been big sources of bugs out in the wild. Much more often there's a wrapper around a browser API or big js library that doesn't handle all of the less common & error modes. I think I have to think more deeply about how much robustness to weird platform behavior (for instance in older browsers) having the application core live in Elm would buy us.
On Wednesday, October 11, 2017 at 2:33:00 PM UTC-7, Rupert Smith wrote: > > On Tuesday, October 10, 2017 at 8:55:44 PM UTC+1, Gareth Ari Aye wrote: >> >> * react and redux for managing components and application state >> > > This is the part that is most like Elm, so you might consider porting that > to Elm first? > -- 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.
