> My experience has been that the complexity of managing all those moving parts could be greater than the benefits of using Elm. > It it were my project, I would probably just leave things as is and squash as many bugs as you can until things stabilize a bit. > But if you are considering a total re-write - maybe try it with Elm?
Yeah that sounds like a totally reasonable strategy. I would say that the largest number of bugs have stemmed from inconsistent platform API behavior across browsers. I really like the idea with Elm of building robustness to things like random, buggy IE behaviors. The codebase has definitely outgrown its original architecture so I'm definitely interested in a full rewrite -- I just want to make sure that the frontend language we choose will scale to address many of the issues the previous iteration ran into out in the wild. > (By the way, I have used pdfjs in an Elm project through ports and it worked just fine.) That's awesome! Is that open source? On Wednesday, October 11, 2017 at 9:27:24 AM UTC-7, Rex van der Spuy wrote: > > > Does anyone have experiences to share around using Elm in the context of a >> great number of complex platform and js dependencies? How involved would it >> be to abstract these non-elm dependencies behind ports? Is there a tool >> analogous to caniuse.com that would let me easily figure out which >> platform APIs have already been packaged up nicely for elm usage? >> > > My experience has been that the complexity of managing all those moving > parts could be greater than the benefits of using Elm. > It it were my project, I would probably just leave things as is and squash > as many bugs as you can until things stabilize a bit. > But if you are considering a total re-write - maybe try it with Elm? > > (By the way, I have used pdfjs in an Elm project through ports and it > worked just fine.) > -- 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.
