Well, firstly, thanks for the fantastic tool. About the topic of this post, I would question your statement that "I don't believe that allowing the inclusion of multiple files meets the criterion of enabling better conversations about Elm online." Specifically, you may want to give an example to someone about how to better design your application by using, say, opaque types. Or how some logic may best be separated in a specific module, or how to decide which functions should be exposed, etc. The code may be simple and short, but there's no good way to show this with a single file.
I addressed your comment directly in the post just 1 paragraph later:
I've heard a counterpoint that some concepts can't even be explained briefly in Ellie because they depend on having multiple files. Examples include the Elm module system itself and opaque types. My response to this is is just that the number of concepts in this category is pretty small and I'd rather Ellie be unusable in this small set of cases than split the focus of Ellie between concise conversation and large projects, making it worse at both.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, firstly, thanks for the fantastic tool. About the topic of this post, I would question your statement that "I don't believe that allowing the inclusion of multiple files meets the criterion of enabling better conversations about Elm online." Specifically, you may want to give an example to someone about how to better design your application by using, say, opaque types. Or how some logic may best be separated in a specific module, or how to decide which functions should be exposed, etc. The code may be simple and short, but there's no good way to show this with a single file.
I addressed your comment directly in the post just 1 paragraph later: