Issue #13


"Why am I leaving Elm?" - this is probably the most controversial blog post I've seen in Elm, and I would say it in a positive way because it caused a lot of discussions and allowed people to share different opinions. I think I agree with some points Luke makes, especially the transparency and the future plans. He points at the Django development process and roadmap which is quite transparent and predictable. Compare that to Elm where you have no idea where it's heading and when, and I think it should borrow some of the management ideas from Python and Django community. Have a read if you want to look at the Elm community from another perspective too, whether you think it's right or wrong. Here's a discussion thread on Reddit and HN. Evan also followed up on Twitter.

In "Visualizing Every Elm Package" Matt Brandly wrote the code to visualize the dependencies of every published Elm package.

Elm package dependencies by Matt Brandly

The two large dots on the image are both Elm Core, just different versions. The visualization tells the story about the language and its evolution, how some packages moved to Elm 0.19 and others were left with 0.18. Reminds me the situation with Python 2 and 3.

Are you writing animations in Elm? Matt Griffith has released Elm Animator for making it easier to animate timelines. And Alex Korban wrote a nice introductory article explaining how to use it in your projects.


Elm Review has hit version 2. Think of it as ES Lint (if you're coming from JavaScript). For our projects at work we use ES Lint with AirBnB's ruleset which gives a nice guideline as to how you should structure the code. Elm Review is a project with similar goals: you can create your own rules as to how the code should be structured, how to name variables, etc.

After learning about Elm and deciding that I want to build a project with it, I started looking into i18n solutions. That area still feels like a wild west to me and has frustrated others (just read "Why I'm leaving Elm"). One of the approaches is to use web components to interact between Elm and JavaScript. Wolfgang Schuster has made such component. Link

Michael Weiss has built a toolkit to create rich text editors. While it's not a drop-in replacement for any text editor you might have, it is fairly easy to build a simple editor using this code. While building the toolkit, Michael also shared some of his thought process in an insightful blog post. And soonafter Elm community followed with some examples.

Show Comments