Elm Tricks from Production–Intro
Elm Tricks from Production (Series)Elm Tricks from Production–Intro Elm Tricks from Production–Migrating from Angular v1 to Elm Elm Tricks from Production–Declarative, Bug-Free User Interfaces with Custom Types Elm Tricks from Production–Adding Event Listeners to DOM Nodes that do not yet Exist Elm Tricks from Production–Automated Testing is Just Another Tool Elm Tricks from Production–From Angular v1 to Elm in 4 Days
We are happy to announce the release of a new version of AirCasting!
This is exciting for us because the application not only has a new look and many new features. There’s also been a lot of work on the infrastructure, performance and technology.
Being a seven-year-old product, it had accumulated some rust. In fact, AirCasting has been using the first version of Angular since inception. Unfortunately, using an outdated web framework from 2010 makes work cumbersome and slow. That translates into higher costs, many bugs and a lot of frustration.
Gladly, this last iteration was about revamping the entire user interface: the perfect excuse to introduce a new technology, cut costs and improve the product.
At Lunar Logic we have our group of functional programming aficionados: we have used Elm, “a delightful language for reliable webapps”, in the past and decided to do the same for AirCasting. Our experience has confirmed once again how great of a technology Elm is. In particular, in the last few months of use we have noticed:
A dramatic decrease of bugs: the Elm type system prevents invalid states and catches a lot of problems in development, way before the code gets to production.
Changing code is like a walk in the park: in Elm we say “if it compiles, it works”. That means once the program is written and it works as expected, it’s really easy to modify or add new features.
It’s a joy to work with: developers have a great time working with Elm, users enjoy error-free applications and stakeholders can build features fast and effortlessly.
In other words, Elm enables fast iterations, cutting costs and keeping everybody happy. But don’t take our word for it, this is a testimonial by Michael Heimbinder, Founder & Executive Director of HabitatMap (AirCasting):
Moving AirCasting from Angular to Elm has simplified the process of developing new features and identifying and zapping bugs. The comparative ease of working in Elm makes for better communication between members of the development team, which results in better code in less time
The Elm community is not as mainstream as React’s and Angular’s. Therefore, the ecosystem is smaller and fewer developers are up-to-speed with the technology. We argue that it doesn’t really matter how big an ecosystem is, as long as it’s big enough. When it comes to programmers, we expect to attract the people who became dissatisfied with traditional approaches and challenged the status quo. At NoRedInk that is already reality:
Elm is the #1 reason developers apply
Since AirCasting is powered mostly by Elm now, we have decided to publish an “Elm Tricks from Production” blog series. So fasten your seatbelt and get ready to see:
- why Elm is the best;
- why AirCasting is cool;
- real Elm code from production;
- what concepts Elm entails that could be applied in other languages / frameworks.
I need your help to make the blog awesome. Here's a survey. Since there are no required questions, you decide how much time to spend on it.
Support my work by tweeting this article! 🙏