Have you been using outside libraries that were written in javascript on these projects?
I always anticipated that would be a downside of using Elm. I know there must be hooks to let you integrate pure javascript (jQuery-type) libraries and widgets into your app, but wouldn't it be really annoying?
I'm writing Angular apps these days and one of the most time-consuming tasks is this sort of integration (for instance, right now I'm trying to add FullCalendar [0] to an app), and it doesn't work so nicely with the digest cycle of Angular, or play nicely with how data is passed around. And Elm is even more alien to javascript than a javascript app using Angular would be to javascript. So how is this area for you?
I guess my approach is different. I only use a library when I have to, meaning that it's of "high quality" and it will save lots of time.
Otherwise, I'd rather implement the feature myself, so I know the code and I can extend it later.
In that sense, Elm covers me completely. There are many small good utility libraries to use, but I only use 2-3 of them.
And most of them, you can read the code, quickly understand what it does and pick the code you want to use in your app.
I always anticipated that would be a downside of using Elm. I know there must be hooks to let you integrate pure javascript (jQuery-type) libraries and widgets into your app, but wouldn't it be really annoying?
I'm writing Angular apps these days and one of the most time-consuming tasks is this sort of integration (for instance, right now I'm trying to add FullCalendar [0] to an app), and it doesn't work so nicely with the digest cycle of Angular, or play nicely with how data is passed around. And Elm is even more alien to javascript than a javascript app using Angular would be to javascript. So how is this area for you?
[0] https://fullcalendar.io/