With regards to working with binary files, what all does that entail? I assume support for typed-arrays and ArrayBuffer... anything else?
On Sunday, December 11, 2016 at 3:59:08 PM UTC-6, Zinggi wrote: > > (Elm discuss is fine for this. There are almost no open discussions on elm > dev, as these are usually a waste of everyone's time.) > > For me, these things would be nice to have: > * WebAudio API > * File upload > * Working with binary files, e.g. parsing > * Persistent cache, offering access to local storage and maybe also > IndexedDB > (It's already there, but not released yet: > https://github.com/elm-lang/persistent-cache) > * Gamepad API > > > On Sunday, 11 December 2016 21:17:50 UTC+1, W. Brian Gourlie wrote: >> >> Per the elm-dev mailing list guidelines, I don't think this would be >> appropriate there. I'm also mostly interested in what other users feel are >> shortcomings. Perhaps if I had a curated list of things, I could try and >> bring it to the devs attention. >> >> On Sunday, December 11, 2016 at 10:09:55 AM UTC-6, Duane Johnson wrote: >>> >>> I think this list is for discussion and is not as frequented by the elm >>> core developers, so you might try >>> https://groups.google.com/forum/?fromgroups#!forum/elm-dev >>> >>> They still show up here on occasion, but my impression is that they >>> primarily hang out over there. >>> >>> On Sat, Dec 10, 2016 at 3:03 PM, W. Brian Gourlie <[email protected]> >>> wrote: >>> >>>> I've noticed a fair amount of discussion around various shortcomings of >>>> Elm's native libraries. Particular examples that affect me are the limited >>>> Websocket API and no native typed-array implementation. The former is >>>> limits me quite a bit, while the latter is simply a nice-to-have. I've >>>> seen >>>> clamoring for file upload support as well. In any event, it would be >>>> interesting to get an idea of what people feel are the Elm's biggest >>>> shortcomings in terms of natively supported features. >>>> >>>> One thing that is frustrating as an Elm user is feeling in the dark >>>> when it comes to feature requests. I know the team likes to batch their >>>> efforts, but it's disheartening to see something sit for months >>>> unanswered. >>>> I'm hoping for two things to come out of this post: Get an idea of what >>>> the >>>> biggest pain points are in terms of natively supported API's, and to get >>>> an >>>> idea of what the Elm devs think. Any feedback really would be nice! >>>> >>>> Brian >>>> >>>> -- >>>> 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. >>>> >>> >>> -- 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.
