1) Futures 2) Binary data 3) Audio On Saturday, December 10, 2016 at 5:03:08 PM UTC-5, W. Brian Gourlie 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.
