It's easy to be a silent observer when none of a thread applies to you. But I feel like I need to throw in here that Elm has been working great for the SPA I've been building. I transitioned to Elm from Ember 3 months ago and couldn't be happier.
I also recognize that Elm is still a pre-1.0 language/framework—I have full confidence that the issues raised here and elsewhere will be put to rest eventually. Regardless, Elm works great for me as it is now. Dustin > On Apr 25, 2017, at 12:42 PM, Eirik Sletteberg <[email protected]> > wrote: > > Since you mention pitch forks... > Maybe there's a potential for an Elm fork. Something like io.js was for > node.js, until they re-merged. A fork which encourages community involvement > in the form of code patches/pull requests, even to the compiler and the core > library (maybe even adding new syntax to the language), and an open ecosystem > where anybody can publish packages. (Maybe build a package ecosystem > piggybacked on top of npm, instead of elm's own package manager). It could > support task ports, which many people think would provide much better interop > between Elm and JS. A fork governed and maintained by multiple people. > Features from the fork could be merged back into Elm upstream if they > succeed, or they could be discarded. > > > tirsdag 25. april 2017 17.23.20 UTC+2 skrev Erik Lott følgende: > Does anybody has an idea how other languages/platforms manage to get > community involved? > > The elm community will grow organically if it's given the chance. However, to > have a thriving and exciting community, at a minimum, developers need to be > able to actively write, contribute and share packages with each other, > without the language creators being involved in that loop. > > Unfortunately, the only solutions to the current holes and under-developed > areas of the web api are either to use ports or native modules (hack), > neither of which are acceptable solutions for developing blessed community > packages. So we're blocked... > > The foundation of the language isn't quite ready for explosive community > growth yet, so expect to see a lot of pitch forks and torches until it is. > > > > > > On Tuesday, April 25, 2017 at 9:27:49 AM UTC-4, Wojtek Piekutowski wrote: > The number of similar voices regarding community process and amount of > frequently requested missing features/native libraries (like binary support > and better JS interop) show a problem. No matter how amazing and performant > Elm will ever be, newcomers will be discouraged by everlasting begging for > native APIs support. > > Does anybody has an idea how other languages/platforms manage to get > community involved? I think it could be beneficial to learn from, for example > Elixir community, and borrow some good practices that could work for Elm too. > > On Tue, 25 Apr 2017 at 05:22, Duane Johnson <[email protected] <>> wrote: > As several have asked, and Peter Damoc kindly reached out off-list, I'll post > here what I wrote to him. Please know that I do appreciate what everyone has > worked on, but this hasn't worked for me for the reasons I outline. I've > started auto-archiving email from elm-discuss, so if you have any questions, > please reach out to me off-list. Thanks. > > Hi Peter, that's kind of you to follow up off-list. > > I've had several pain points. I'll go over the technical ones first and the > community ones second. > > In the two (and a half) projects that failed, they failed for different > reasons but in general, because of JS interop issues. In the first project, I > was unable to access binary data in order to represent compiled hex blobs as > visual SVG (see https://github.com/canadaduane/elm-hccb/tree/master > <https://github.com/canadaduane/elm-hccb/tree/master>). I made a use case > post here > https://groups.google.com/d/msg/elm-discuss/spr621OlUeo/awhuqzpzBgAJ > <https://groups.google.com/d/msg/elm-discuss/spr621OlUeo/awhuqzpzBgAJ>. > > In the second case, I was trying to create custom elements that could be > embedded inside the QuillJS rich text editor--in other words, it wasn't > enough just to treat Javascript as an external API, I needed to embed elm > "things" inside a JS component inside elm. > > I made a third attempt to convert an AngularJS app to Elm, but didn't get > very far in and gave up, in part because of the attitude I've felt from the > Elm community that components are bad and have no place here (when everything > I'm seeing in Angular is trying to be more like a component, and interact > with the world like a component). > > The community aspect that has weighed heavily on me is the feeling that I'm > not a participant in the decision-making or priority-setting. I feel more > like a distant user, or maybe an interesting use case, from which data is > gathered and decisions are made (by someone else, somewhere else). > > I hope that helps! > > Thanks again for your reaching out. I really look up to you and eeue56. > > Take care, > Duane > > On Monday, April 24, 2017 at 4:31:08 PM UTC-6, Joe Andaverde wrote: > Duane, > > I'm curious what the roadblocks were in the 2 of 3 you didn't have success > with? This could definitely help others when making their decision. Also, it > may provide helpful feedback to more appropriately prioritize future elm > platform development. > > Thanks! > > On Monday, April 24, 2017 at 8:45:57 AM UTC-5, Duane Johnson wrote: > Hi all, > > I've decided to move on from Elm. I've only been successful in 1 of 3 > projects. I'm now in a role where I need to make an important decision > regarding the transition of a codebase from Angular to something else, and I > don't feel like I can responsibly recommend Elm as the replacement. So I need > to focus my time and effort elsewhere. > > If someone could please remove me as a moderator of elm-discuss it would be > appreciated. > > If anyone is interested in taking the `canadaduane/typed-svg` project over, > I'd be happy to help transition it to willing hands. > > Thanks, > Duane Johnson > aka canadaduane > > > -- > 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 > <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] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- Dustin Farris -- 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.
