Question: What components would you like to use, that you want a UI library for?

Asked By
Asked At
2018-04-01 18:25:46

Found 15 possible answers.

User Answered At Possible Answer
vintem 2018-04-01 19:01:03 Things like, autocomplete, modal windows, sidebar panes, notifications, drag and drop... all of which are things already solved somewhere else, I don't think there's any value spending time re-working on them
peterszerzo 2018-04-01 19:06:47 The lazy version will work in practice in a way identical to React's business:
type alias WidgetConfig msg =
I wonder, from a library user's perspective, is this preferable to making users having to wire up the sub Msg / update/ business? } , toMsg : (WidgetState -> WidgetState) -> msg { state : WidgetState
huscar 2018-04-01 19:20:30 Anyone here used ? I'm curious about experimenting with elm in a microservices context but have not used serverless (the npm package) before so I thought lets see if anyone has user stories first :slightly_smiling_face:
sturgman 2018-04-01 19:47:48 Can someone help me understand how to read these performance plots? What exactly are the horizontal and vertical axes?
alex670 2018-04-01 20:10:47 I'm curious too
ilias 2018-04-01 20:15:30 horizontal is the size of the list, vertical is the number of list-items processed per second For very small lists, things like the overhead of calling a function dominate. When you go a little further along, things tend to settle a bit. Eventually, garbage collection needs to kick in every now and then because foldr and map tend to create intermediate structures and as the sizes grow, so does the generated garbage. In case of List.foldr , the yellow line also has a drop around 2k, I think I explain that in the readme somewhere
ktosiek 2018-04-01 20:27:20 which reminds me, is there a difference in performance between |> a |> b and |> (a >> b) ? Or is this pattern optimized?
ilias 2018-04-01 20:27:57 Currently there's no fusion/rewriting like that
alex670 2018-04-01 20:27:59 Issue has a reply, so check it out
ilias 2018-04-01 20:29:11 though >> , << , |> and <| do get special treatment in the compiler so that they actually compile to either a lambda or actual application, rather than a runtime-call to the "operator" so f >> g compiles to function (x) { g(f(x)) } and arg |> f |> g to g(f(arg)) , rather than something like ops['>>'](f, g) or ops['|>'](arg, ops['|>](f, g)) or whatever that would become. Anyway, it basically desugars them.
josephferano 2018-04-01 20:35:31 @ktosiek I tried applying that patch but the arrow keys now don't work in either browser :confused: Any other recommendations?
ilias 2018-04-01 20:36:22 So long story short: yeah, there is a difference. The fastest option with the least runtime overhead is to have a named toplevel function c x = a x |> b , if you want to go wild
josephferano 2018-04-01 20:36:38 Let me see if something else is wrong... Is there an elm package that handles keyboard inputs with non-deprecated calls?
ilias 2018-04-01 20:38:07 @josephferano are you using presses or ups ?
josephferano 2018-04-01 20:38:32 Ugh So if I use which instead of keyCode , the problem gets inverted, in firefox I guess I could switch to ups presses

Related Questions