Thank you so much @luke and now @tbash for Ellie.
This tool has revolutionized the way to help people, share examples or collaborate on issues in the Elm community. It is also a great source of real use cases of custom elements (particularly CodeMirror).
Thank you, @evancz, for making Elm so much more approachable for newcomers than its more academically-minded pure-functional relatives. I was brought up in a Lispy world, but where ML and Haskell bounced off of my forehead, Elm has stuck. I am deeply impressed with the quality of the Elm guide generally, and especially its complete lack of academic terminology. I am equally impressed with the precision and helpfulness of the Elm compiler messages. Finally, I am impressed with how deeply you have thought about, and how eloquently you have spoken about, the way in which you are continuing to evolve Elm, and the “hard parts of open source” as it relates to your approach. Thank you.
(Additional shout-outs for general excellence for elm-format, Ellie, and elm-ui; and also for the culture and quality of the Elm Slack. And @joakin, this is an awesome thread. Thank you to everybody!)
Also, thanks to @evancz and @rtfeldman for several of the absolute best videos about programming and the social environment around programming.
@evancz for this beautiful language
@rtfeldman for all the great talks that somehow become defacto references
@halohalospecial for the best elm editor plugin elmjutsu the only reason I’m using Atom now
@harmboschloo for the excellent and underrated graphql-to-elm which maps exactly to how I want to do GraphQL
@supermario for lamdera and the mind expanding discussion and sharing 
♂
@charliek for the Advanced Types in Elm series
@yang-wei and commenters in https://gist.github.com/yang-wei/4f563fbf81ff843e8b1e really helpful when I was learning Elm
@joelq for absolutely everything in https://thoughtbot.com/blog/tags/elm
@Warry @jinjor and @evancz for patience and thoughtful feedback
Thanks to NoRedInk for having the foresight to take @evancz and Elm ‘in-house’. I’m guessing Elm might not be where it is today if you hadn’t provided @evancz with the time and resources to focus fully on Elm.
Thanks to @evancz for such a great language, and for sticking to your principles for where you want Elm to go. I do like the slow, carefully thought-out release cycles, knowing that when a new release arrives there’s good reason for it, and it’s stable.
Thanks to the rest of the core team, I’m sure you do a lot in the background that we don’t get to hear about.
Thanks to @mdgriffith for Elm-UI and now Elm-Animator - they have become the first packages I install when starting a project.
Thanks to @rtfeldman for the great talks on youtube. Your enthusiasm is infectious and is what prompted me to try Elm in the first place. I’ve got your book on MEAP, so I’ll be going through it sometime soon to see what new nuggets I can learn.
Thanks to the whole Elm community here on Discourse, all so friendly and helpful. For someone like me with no techie friends/colleagues to bounce things off, it’s nice to know I can come here when I need to.
Thanks to everyone who has helped me when I needed it.
I never really enjoyed front end ‘stuff’, always preferred server-side with Ruby and Elixir, but, for a long time now a day hasn’t gone by that I haven’t written some Elm code. I’d probably get withdrawal symptoms if I took a break from Elm 
.
Forgot all the great tooling:
Thanks to @razze for LSP-elm.
Thanks to everyone involved with authoring/maintaining elm-test.
Thanks to @dmy for elm-doc-preview
Thanks to @avh4 for elm-format
Thanks to @stoeffel for elm-verify-examples
Big thanks to @wking-io, for elm-live -which is my dev server of choice and makes my life easier- and for the podcast 
What a wonderful idea! I feel the love. 
Thank you all for being such a great group of people! Much love right back to the whole Elm community. 
Just want to hop on and share my thanks as well. Since the “early days” (for me at least) of 0.15, it has been an amazing journey. Elm was my first introduction to a functional language having “grown up” with imperative and object-oriented languages. It really took a mind-shift for me to think functionally, but once I did, wow, I’m so happy.
There have been many over the last years who have helped me through learning curves, concepts, design, and simply making things work… too many to list here. Others here have mentioned many (if not all) who would be on that list.
Let me just say a huge Thank You! to everyone in this community who have contributed and responded and just been a support by showing up; even the little contributions have made a big difference.
Here’s to the future of Elm and a vibrant, welcoming, helpful, gracious community.
(OK - I do have to call out @evancz without whom I would be trying to imagine I was happy with some other web tech stack 
)
My turn!
Thank you @evancz for building Elm. I have had a lot of fun using it ever since I discovered it.
Thank you for being all your excellent design work, and having a long-term vision for the language and sticking to it even when confronted with adversity and critique. Those design decisions are what made working on elm-review so enjoyable, both for writing the tool and as Elm the analysis target.
I now breathe Elm in my spare-time, try to get in front of people talking about Elm, look for Elm jobs and get hired and paid for writing Elm. The impact you have had on my day-to-day life has been meaningful.
Thank you @rtfeldman for giving so many great talks on Elm and inspiring me and others to use it. Watching some of your talks were also a great way to prepare internal company pitches to use Elm (successfully too!). Also, thank you for pushing me a “bit” further with my work on elm-review by telling me “the author is responsible for the user experience”. That sentence alone added 2 more months of work for the initial release, but the result has definitely been worth it. And that mantra is now ingrained in my OSS work.
Thank you @dillonkearns for all your time and great feedback on my work, and for wanting me to do podcasts and live streams with you. It’s an honor and a great deal of fun!
Thank you to the people who help beginners on Slack and help make Elm feel like a warm community. Many help out with that, but I’d like to give a specific shout-out to @jessta, @pd-andy and @joelq for being there so often, for the quality of the help you give and for your so hard-to-beat typing speed.
Thanks a lot to the people who work on the tooling, especially to @avh4 for elm-format, @ilias for elm-json and elm-xref, @stil4m for Elm Analyse and elm-syntax, and @dmy for elm-doc-preview. All of which are immensely useful and/or an inspiration for my projects.
Thank you all, and thanks to all the others I didn’t mention (I’ll blame the limit of 10 mentions) who make this community one I enjoy so much
Thank you to @rtfeldman for writing such an accessible book “Elm in Action” and all three Frontend Masters courses. I doubt there’s any active Elm community in the whole of Africa, and i’ve personally never heard of a meetup in any of the dev communities across Africa, but thanks to these amazing resources, we have a handful of developers learning and building in Elm.
Thanks to @jfairbank and @alexkorban for their amazing resources too.
@evancz thank you for your impressive resolve and fortitude in the face of constant barrage, and your commitment to building such an impressive language.
Thanks to the folks at Elm Town. Your podcasts are amazing
@dillonkearns I don’t think i have enough words for the staggering amount of work you’re putting in. A big thank you
And to a larger extent, everyone in the community doing their little bits to make this beautiful language accessible worldwide. Thank you all.
Thank you @evancz for creating a language that is a joy to work with: elegant, expressive, and powerful despite its simplicity (which is in fact a great virtue). And thank you for that suggestion: “maybe look at elm/parser-tools.” It changed everything for me.
(PS. I think Elm is revolutionary)
Thank you @ilias for helping me over my many first stumbles with elm/parser-tools, and for suggestions about optimizations that transformed one app from painfully slow to blazingly fast.
Thank you @luke for Ellie and for quickly getting me out of what looked like a fatal dead-end on my main project.
Thank you @rtfeldman for inspirational and insightful talks, good advice, and for being such an outstanding advocate for Elm … oh! and for your book!!
Thank you @mdgriffith for elm-ui which I use every day.
There are so many more that have helped me in ways small and large … please forgive me for not listing you all here. You are part of an open, friendly, supportive community that welcomes newcomers and helps them get started and to keep going. And so thank you, thank you to the community at large.
THANK YOU…
@evancz for getting to the crux of FP & for such a brilliant language/community
@mdgriffith for the most enjoyable layout framework ever!!!
@dillonkearns for a fantastic elm-graphql lib we have been relying on
@rtfeldman for great talks, valuable community engagements & some super useful libs
@ianmackenzie for solving so many problems
@supermario for Lamdera
@luke for the fantastic talk shedding light on working with web components
@terezka for an inspiring talk on parsing in Elm; we care!
@avh4 for elm-format (what a time saver)
@halfzebra for create-elm-app - makes it so easy to get started for beginners
Kris for RemoteData
…the list goes on 
Hey @joakin! I think this is a great idea! It’s so important to say thank you:
Open source communities are like precious delicate jewels. A little tick and they can just shatter. It’s made of people, people. We write the code, we support it, we use it, we document it. Releasing code is a very personal thing. You’re showing people, here’s how I think, here’s how I work, here’s how my brain is organized. And if it’s not a healthy place to do that, people aren’t going to be free to express themselves through the code that they release. - Limor Fried (on command-line-heros 18:22)
Thank you for all your contributions, I much appreciate them! Thank you…
@evancz for elm, your talks, your blog posts and everything else you do for this awesome language!
@mic for organizing the elm vienna meetup with me
@tibastral (and all others who helped) for organzing elm europe 2019
@razze for elm lsp
@dillonkearns for elm graphql, talks, blog posts, podcasts
@avh4 for elm format
@mdgriffith for elm-ui
@wking-io for the implementing elm podcast
@kevinyank for elm town
@ rtfeldman for his many contributions to elm (packages, blog posts, talks, and so much more)
@ luke and @ tbash for ellie
@ RyanNHG for elm spa
@ noredink and @ bekk for their investment in elm
And thanks to all the very supporting people on this forum and on slack!
Thanks to the community, @mweiss, @rtfeldman, @alexkorban, @avh4, @klazuka, @mdgriffith, all of you!
But first and foremost, @evancz, thank you for holding your ground!
I am an occasional (not professional) programmer and the Elm community is the place I wish to stay forever. Thank you @evancz and the core team for your thoughtful approach to language features because when I can’t code for a few weeks (or months), the language doesn’t leave me behind. Thank you to the friendly and nurturing community because you make it OK to be a perpetual novice. Thank you Elm programmers for agreeing on conventions like TEA and elm-format so that noobs like me are not paralyzed by the paradox of choice. Thank you authors, speakers, and podcasters. (I think I have bought every Elm book, subscribed to every Elm podcast, and watched every Elm talk and I know that my wife recognizes @rtfeldman’s voice with her eyes closed.) Speaking of voices, thank you for an inclusive atmosphere where we hear voices like @glitteringkatie, @terezka, Tessa Kelly, Emma Cunningham, and @noahzgordon. I don’t think my reply was as concise as possible, but I hope that you’ll forgive me.
I mulled over this for a bit, trying to nail what’s really important to me, and what it is I actually love about Elm. And what keeps me coming back is how readable the code is. Both the lack of sigils, keywords, and so on, strong compile guarantees, and low number of features to be aware of, but also the tooling for formatting and navigating the code; they all add up to make (most) code very easy to read and reason about, and this always brings a sigh of relief to my grey matter after I’ve been reading code in different languages.
So thank you very much to @evancz, @avh4, and @klazuka (amongst others) for a combination of language and tooling that makes reading code so pleasant 
I nod my head to every one listed so far. This community is great and there are a lot of great minds at work here. Instead of repeating what everyone else has said before, I would like to give a toast to the - in my mind - best package authors in our community:
@mdgriffith for mdgriffith/elm-ui.
@avh4 for avh4/elm-color.
@arowM for arowM/elm-form-decoder
@turboMaCk for turboMaCk/any-dict, turboMaCk/any-set and turboMaCk/queue
@ianmackenzie for ianmackenzie/elm-geometry and ianmackenzie/elm-geometry-svg
And for the best package of them all
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.