IssueRaiser

Why We Still Choose (and Recommend) Elm in 2024?

# Why? In 2016 when we were considering our options for how to build an upcoming web app/project, we opened the "***Why***?" issue #1 to capture our initial reasoning for shortlisting Elm. In the interest of _balance_ we _also_ opened a "**Why _NOT_**?" #2 to concisely capture the _counter-points_. _Sadly_, `some` people have _chosen_ to focus on the "Why NOT?" from ***2016*** and _ignore_ the fact that _everything_ in Elm-lang and it's _wonderful_ community has gotten _much_ better in the last **27 Months**! # _Who_ is this for? If you have _already_ made up your mind on your technology choices for whatever reason and are a die-hard fan of a particular language, framework or paradigm, this is _not_ for you. _Thank you_ for reading this far and _have a **great day**_! This post is for anyone who is either _considering_ what programming language / architecture to use for their web application or is joining a team that _already_ has an Elm App and wants to _understand_ the reasoning behind why the Elm language and architecture is the _appropriate_ choice for the project. Our goal is to help Lead developers or CTOs have a _reference_ they can share with their team which _comprehensively_ illustrates the **_business_ case** for _why_ choosing Elm will _directly/objectively_ result in a better _user experience_ (_faster page load time, no errors and more responsive UI!_), better developer experience (_friendly compiler warnings, faster compilation and clear upgrade instruc

Posted by nelsonic on Feb 21, 2019, 8:20 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.4,000 issues0 comments

ux (SaaS)

Why We Still Choose (and Recommend) Elm in 2024?

nelsonicFeb 21, 2019, 8:20 PM

# Why? In 2016 when we were considering our options for how to build an upcoming web app/project, we opened the "***Why***?" issue #1 to capture our initial reasoning for shortlisting Elm. In the interest of _balance_ we _also_ opened a "**Why _NOT_**?" #2 to concisely capture the _counter-points_. _Sadly_, `some` people have _chosen_ to focus on the "Why NOT?" from ***2016*** and _ignore_ the fact that _everything_ in Elm-lang and it's _wonderful_ community has gotten _much_ better in the last **27 Months**! # _Who_ is this for? If you have _already_ made up your mind on your technology choices for whatever reason and are a die-hard fan of a particular language, framework or paradigm, this is _not_ for you. _Thank you_ for reading this far and _have a **great day**_! This post is for anyone who is either _considering_ what programming language / architecture to use for their web application or is joining a team that _already_ has an Elm App and wants to _understand_ the reasoning behind why the Elm language and architecture is the _appropriate_ choice for the project. Our goal is to help Lead developers or CTOs have a _reference_ they can share with their team which _comprehensively_ illustrates the **_business_ case** for _why_ choosing Elm will _directly/objectively_ result in a better _user experience_ (_faster page load time, no errors and more responsive UI!_), better developer experience (_friendly compiler warnings, faster compilation and clear upgrade instruc

Comments (0)

No comments yet. Start the discussion.

Comment on this issue