Hi, I am working on the 2022 edition of the “Elm, a year in review” post.
If you made something in 2022 related to Elm (a tool, a presentation, a post, anything!), or you know an interesting project, I would appreciate it if you have a look at the draft version and make sure that it is listed there.
If it is not listed, or if you would like to suggest any editing, please open an issue, a pull request, or send me a message.
This is a really valuable contribution, both to the existing Elm community and for prospective new users of Elm. The reply to the perennial “Is Elm Dead?” posts should be simply a link to the most recent version of this document!
I’ve been running my business on Elm for years, but can’t showcase what we have done because they are internal projects for customers.
Companies in the same position as mine are also part of the strength of Elm in the community, and I think it would be good to represent them in some way in the “Year in Review”.
I continued to work on Mammudeck in 2022 (started in 2019). Mammudeck is a TweetDeck-like, multi-column user interface for the Mastodon client API. It works on desktop or mobile. I use it every day for multiple Fediverse sites. Next projects: editing posts in Rebased, quoted posts in Rebased, global persistence with DynamoDB (currently, persistence uses LocalStorage, so is only for one browser).
Which is why Mammudeck will use each user’s DynamoDB account. I’m not going into the content storage business. The tiny amount of data that Mammudeck needs is so small that it will be pennies per month for a single user, or less.
How did you determine which companies are using Elm? I think it would be a good idea to note in the year in review post what the source of the data is.
elm-widgets.netlify.app , tho released on January 1, 2023 was first announced on the last elm remote meetup and the alpha repository was getting tested last year’s second semester!