I don't love the idea of furthering this thread, but felt I'd take a swing at something I think is kind of core to the Elm community (and has been communicated as such):
- There is a limited amount of time that can be spent on Elm (this is true of all things) - To maximize the benefit/time ratio of work being done, it is best to have a motivating use case to identify actual use cases that are problematic. - Once one has been identified, writing up a short (because there's limited time, again) explanation of the real world problem that you are experiencing, coupled with an SSCCE <http://sscce.org/>, is the best way to communicate the problem you're having - both the motivating use case and the initial work that's gone into identifying the core problem. *Inside of this framework*, I've seen extremely meaningful discussions occur. *Outside of this framework*, I've witnessed a lot of threads that serve to rile people up but don't meaningfully benefit the language. I would love a do-over of this thread. If you have a real-world problem that you can share with us, we can all work on seeing what we can do to help. If you don't, we'll talk about micro-optimizations. As one example, Noah mentioned that there was a real-world problem related to this, and by modeling the data in a slightly different way they were able to solve it. If we had a similar situation perhaps a similar result could ensue. My $0.02. (given the number of words, it seems my opinions are *cheap*) Joshie -- 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.
