# Working on "Elm 2022, a year in review"

**URL:** <https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877>\
**Category:** Request Feedback\
**Created:** [January 9, 2023, 10:12pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877 "2023-01-09T22:12:09Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![lucamug](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lucamug/32/1764_2.png) [@lucamug](https://discourse.elm-lang.org/u/lucamug)\
**Post date:** [January 9, 2023, 10:12pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/1 "2023-01-09T22:12:09Z")

</div>

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.

Draft: [Main2022](https://lucamug.github.io/elm-a-year-in-review/)  
Repo: [GitHub - lucamug/elm-a-year-in-review](https://github.com/lucamug/elm-a-year-in-review)  
For reference, this is the version of 2021: [Elm 2021, a year in review - DEV Community 👩‍💻👨‍💻](https://dev.to/lucamug/elm-2021-a-year-in-review-4pho)

Thank you!

---

<div class="post-metadata">

**Author:** ![jxxcarlson](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/jxxcarlson/32/866_2.png) [@jxxcarlson](https://discourse.elm-lang.org/u/jxxcarlson)\
**Post date:** [January 10, 2023, 2:19pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/2 "2023-01-10T14:19:08Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![dirkbj](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/dirkbj/32/3162_2.png) [@dirkbj](https://discourse.elm-lang.org/u/dirkbj)\
**Post date:** [January 10, 2023, 8:52pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/3 "2023-01-10T20:52:35Z")

</div>

This is amazing!

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”.

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 11, 2023, 1:17am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/4 "2023-01-11T01:17:48Z")

</div>

I just put in a PR to remove dead links from elm-companies github repo, so that has an accurate list of most elm commercial users.

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 11, 2023, 1:19am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/5 "2023-01-11T01:19:03Z")

</div>

- link to this blog post in the “Welcome” message for this forum.

---

<div class="post-metadata">

**Author:** ![jxxcarlson](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/jxxcarlson/32/866_2.png) [@jxxcarlson](https://discourse.elm-lang.org/u/jxxcarlson)\
**Post date:** [January 11, 2023, 1:24pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/6 "2023-01-11T13:24:42Z")

</div>

I’ve stumbled across three pretty significant Elm projects that are not generally known or talked about. Would be good to have better data.

---

<div class="post-metadata">

**Author:** ![billstclair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/billstclair/32/260_2.png) [@billstclair](https://discourse.elm-lang.org/u/billstclair)\
**Post date:** [January 11, 2023, 1:42pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/7 "2023-01-11T13:42:50Z")

</div>

I continued to work on [Mammudeck](https://Mammudeck.com) 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).

Open source: [GitHub - billstclair/mammudeck: A Tweetdeck-like interface to the Mastodon social media platform](https://github.com/billstclair/mammudeck)

billstclair/elm-dynamodb does a small subset of the Amazon DynamoDB API: [elm-dynamodb 2.3.0](https://package.elm-lang.org/packages/billstclair/elm-dynamodb/latest/)

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 11, 2023, 9:07pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/8 "2023-01-11T21:07:33Z")

</div>

In my brief exposure to dynamodb, I remember hearing that it gets very expensive to use compared to other options.

---

<div class="post-metadata">

**Author:** ![billstclair](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/billstclair/32/260_2.png) [@billstclair](https://discourse.elm-lang.org/u/billstclair)\
**Post date:** [January 11, 2023, 9:23pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/9 "2023-01-11T21:23:23Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![lucamug](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lucamug/32/1764_2.png) [@lucamug](https://discourse.elm-lang.org/u/lucamug)\
**Post date:** [January 16, 2023, 8:47am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/10 "2023-01-16T08:47:38Z")

</div>

I updated it based on feedbacks and added a list of companies that use Elm at the bottom:

[https://lucamug.github.io/elm-a-year-in-review/](https://lucamug.github.io/elm-a-year-in-review/)

---

<div class="post-metadata">

**Author:** ![MartinS](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/martins/32/3137_2.png) [@MartinS](https://discourse.elm-lang.org/u/MartinS)\
**Post date:** [January 16, 2023, 10:12am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/11 "2023-01-16T10:12:34Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![lucamug](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lucamug/32/1764_2.png) [@lucamug](https://discourse.elm-lang.org/u/lucamug)\
**Post date:** [January 16, 2023, 12:22pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/12 "2023-01-16T12:22:51Z")

</div>

Mainly from [GitHub - jah2488/elm-companies: 🌲 A list of companies using Elm in production.](https://github.com/jah2488/elm-companies) and [https://www.elmweekly.nl/](https://www.elmweekly.nl/). Yes, good idea, I will add a note.

---

<div class="post-metadata">

**Author:** ![RyanNHG](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/ryannhg/32/5162_2.png) [@RyanNHG](https://discourse.elm-lang.org/u/RyanNHG)\
**Post date:** [January 16, 2023, 7:58pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/13 "2023-01-16T19:58:46Z")

</div>

It’s not 1.0 yet, so maybe we should wait until 2023– but I started sharing Elm Land back in August:

> <https://twitter.com/rhg_dev/status/1564083453792030724?t=qL72UlqAERT-bD7_hoeIHg&s=19>

There are two blog posts there, one from October and another in December:

> **[Elm Land | Reliable web apps for everyone](https://elm.land)**
>
> Reliable web apps for everyone. A production-ready framework for building Elm applications. Build your next app with confidence, step by step.

---

<div class="post-metadata">

**Author:** ![georgesboris](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/georgesboris/32/3598_2.png) [@georgesboris](https://discourse.elm-lang.org/u/georgesboris)\
**Post date:** [January 16, 2023, 11:59pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/14 "2023-01-16T23:59:17Z")

</div>

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! 🙂

---

<div class="post-metadata">

**Author:** ![georgesboris](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/georgesboris/32/3598_2.png) [@georgesboris](https://discourse.elm-lang.org/u/georgesboris)\
**Post date:** [January 17, 2023, 12:44am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/15 "2023-01-17T00:44:13Z")

</div>

oh! and we also use Elm heavily at [uncover.co](http://uncover.co)

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 18, 2023, 3:55am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/16 "2023-01-18T03:55:56Z")

</div>

Maybe you can add significant new versions of heavily used/downloaded libraries. That is usually what gets me personally most excited.

---

<div class="post-metadata">

**Author:** ![lucamug](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lucamug/32/1764_2.png) [@lucamug](https://discourse.elm-lang.org/u/lucamug)\
**Post date:** [January 20, 2023, 10:40pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/17 "2023-01-20T22:40:41Z")

</div>

That would be good, but I don’t know how to get this data

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 20, 2023, 10:48pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/18 "2023-01-20T22:48:21Z")

</div>

I’ll build it up and post it here.

---

<div class="post-metadata">

**Author:** ![lucamug](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/lucamug/32/1764_2.png) [@lucamug](https://discourse.elm-lang.org/u/lucamug)\
**Post date:** [January 22, 2023, 1:06am UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/19 "2023-01-22T01:06:49Z")

</div>

That would be great! Are you planning to make something automatic, or manual?

---

<div class="post-metadata">

**Author:** ![kanishka](https://avatars.discourse-cdn.com/v4/letter/k/3e96dc/32.png) [@kanishka](https://discourse.elm-lang.org/u/kanishka)\
**Post date:** [January 22, 2023, 5:57pm UTC](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877/20 "2023-01-22T17:57:27Z")

</div>

I will work on manual and consider automating next year

[Next page](https://discourse.elm-lang.org/t/working-on-elm-2022-a-year-in-review/8877.md?page=2)