Alternatives to Elm logo

Alternatives to Elm

TypeScript, React, PureScript, ReasonML, and Haskell are the most popular alternatives and competitors to Elm.
619
684
+ 1
301

What is Elm and what are its top alternatives?

Writing HTML apps is super easy with elm-lang/html. Not only does it render extremely fast, it also quietly guides you towards well-architected code.
Elm is a tool in the Languages category of a tech stack.
Elm is an open source tool with GitHub stars and GitHub forks. Here’s a link to Elm's open source repository on GitHub

Top Alternatives to Elm

  • TypeScript
    TypeScript

    TypeScript is a language for application-scale JavaScript development. It's a typed superset of JavaScript that compiles to plain JavaScript. ...

  • React
    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • PureScript
    PureScript

    A small strongly typed programming language with expressive types that compiles to JavaScript, written in and inspired by Haskell. ...

  • ReasonML
    ReasonML

    It lets you write simple, fast and quality type safe code while leveraging both the JavaScript & OCaml ecosystems.It is powerful, safe type inference means you rarely have to annotate types, but everything gets checked for you. ...

  • Haskell
    Haskell

    It is a general purpose language that can be used in any domain and use case, it is ideally suited for proprietary business logic and data analysis, fast prototyping and enhancing existing software environments with correct code, performance and scalability. ...

  • Svelte
    Svelte

    If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads. ...

  • Elixir
    Elixir

    Elixir leverages the Erlang VM, known for running low-latency, distributed and fault-tolerant systems, while also being successfully used in web development and the embedded software domain. ...

  • JavaScript
    JavaScript

    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles. ...

Elm alternatives & related posts

TypeScript logo

TypeScript

63.4K
49K
463
A superset of JavaScript that compiles to clean JavaScript output
63.4K
49K
+ 1
463
PROS OF TYPESCRIPT
  • 163
    More intuitive and type safe javascript
  • 97
    Type safe
  • 73
    JavaScript superset
  • 46
    The best AltJS ever
  • 27
    Best AltJS for BackEnd
  • 14
    Powerful type system, including generics & JS features
  • 10
    Nice and seamless hybrid of static and dynamic typing
  • 9
    Aligned with ES development for compatibility
  • 9
    Compile time errors
  • 6
    Structural, rather than nominal, subtyping
  • 5
    Angular
  • 3
    Starts and ends with JavaScript
  • 1
    Garbage collection
CONS OF TYPESCRIPT
  • 4
    Code may look heavy and confusing
  • 3
    Hype

related TypeScript posts

Yshay Yaacobi

Our first experience with .NET core was when we developed our OSS feature management platform - Tweek (https://github.com/soluto/tweek). We wanted to create a solution that is able to run anywhere (super important for OSS), has excellent performance characteristics and can fit in a multi-container architecture. We decided to implement our rule engine processor in F# , our main service was implemented in C# and other components were built using JavaScript / TypeScript and Go.

Visual Studio Code worked really well for us as well, it worked well with all our polyglot services and the .Net core integration had great cross-platform developer experience (to be fair, F# was a bit trickier) - actually, each of our team members used a different OS (Ubuntu, macos, windows). Our production deployment ran for a time on Docker Swarm until we've decided to adopt Kubernetes with almost seamless migration process.

After our positive experience of running .Net core workloads in containers and developing Tweek's .Net services on non-windows machines, C# had gained back some of its popularity (originally lost to Node.js), and other teams have been using it for developing microservices, k8s sidecars (like https://github.com/Soluto/airbag), cli tools, serverless functions and other projects...

See more
Adebayo Akinlaja
Engineering Manager at Andela · | 27 upvotes · 1.1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more
React logo

React

128.1K
104.4K
3.8K
A JavaScript library for building user interfaces
128.1K
104.4K
+ 1
3.8K
PROS OF REACT
  • 774
    Components
  • 657
    Virtual dom
  • 567
    Performance
  • 491
    Simplicity
  • 438
    Composable
  • 176
    Data flow
  • 162
    Declarative
  • 124
    Isn't an mvc framework
  • 114
    Reactive updates
  • 111
    Explicit app state
  • 39
    JSX
  • 23
    Learn once, write everywhere
  • 19
    Uni-directional data flow
  • 17
    Easy to Use
  • 14
    Works great with Flux Architecture
  • 10
    Great perfomance
  • 8
    Built by Facebook
  • 7
    Javascript
  • 5
    Speed
  • 5
    TypeScript support
  • 4
    Feels like the 90s
  • 4
    Hooks
  • 4
    Awesome
  • 4
    Scalable
  • 4
    Easy to start
  • 3
    Server Side Rendering
  • 3
    Fancy third party tools
  • 3
    Props
  • 3
    Obama
  • 3
    Server side views
  • 3
    Functional
  • 3
    Scales super well
  • 3
    Excellent Documentation
  • 3
    Cross-platform
  • 2
    Rich ecosystem
  • 2
    Start simple
  • 2
    Allows creating single page applications
  • 2
    Sdfsdfsdf
  • 2
    Beautiful and Neat Component Management
  • 2
    Very gentle learning curve
  • 2
    Has functional components
  • 2
    Simple
  • 2
    Closer to standard JavaScript and HTML than others
  • 2
    Super easy
  • 2
    Has arrow functions
  • 2
    Strong Community
  • 2
    Great migration pathway for older systems
  • 2
    SSR
  • 2
    Fast evolving
  • 2
    Simple, easy to reason about and makes you productive
  • 2
    Just the View of MVC
  • 1
    Sharable
  • 1
    Every decision architecture wise makes sense
  • 1
    Permissively-licensed
  • 1
    Split your UI into components with one true state
  • 1
    Fragments
  • 0
    Recharts
CONS OF REACT
  • 36
    Requires discipline to keep architecture organized
  • 23
    No predefined way to structure your app
  • 22
    Need to be familiar with lots of third party packages
  • 9
    JSX
  • 7
    Not enterprise friendly
  • 5
    One-way binding only
  • 2
    State consistency with backend neglected
  • 2
    Bad Documentation
  • 1
    Paradigms change too fast

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.9M views

I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

See more
Adebayo Akinlaja
Engineering Manager at Andela · | 27 upvotes · 1.1M views

I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

See more
PureScript logo

PureScript

58
68
6
A strongly-typed language that compiles to Javascript
58
68
+ 1
6
PROS OF PURESCRIPT
  • 4
    Purely functional
  • 2
    Great FFI to JavaScript
  • 0
    More Haskell-ish than Haskell
CONS OF PURESCRIPT
  • 1
    Have Some Bugs

related PureScript posts

ReasonML logo

ReasonML

68
79
9
A friendly programming language for JavaScript and OCaml
68
79
+ 1
9
PROS OF REASONML
  • 4
    Pattern Matching
  • 3
    Type System
  • 1
    Fun
  • 1
    React
CONS OF REASONML
  • 1
    Bindings

related ReasonML posts

Haskell logo

Haskell

1.1K
1.1K
495
An advanced purely-functional programming language
1.1K
1.1K
+ 1
495
PROS OF HASKELL
  • 86
    Purely-functional programming
  • 65
    Statically typed
  • 58
    Type-safe
  • 38
    Great community
  • 38
    Open source
  • 29
    Composable
  • 29
    Built-in concurrency
  • 28
    Built-in parallelism
  • 22
    Referentially transparent
  • 19
    Generics
  • 14
    Intellectual satisfaction
  • 13
    Type inference
  • 11
    If it compiles, it's correct
  • 7
    Flexible
  • 7
    Monads
  • 4
    Great type system
  • 4
    Proposition testing with QuickCheck
  • 3
    One of the most powerful languages *(see blub paradox)*
  • 2
    Great maintainability of the code
  • 2
    Fun
  • 2
    Purely-functional Programming
  • 2
    Kind system
  • 2
    Reliable
  • 2
    Highly expressive, type-safe, fast development time
  • 2
    Type classes
  • 2
    Better type-safe than sorry
  • 2
    Pattern matching and completeness checking
  • 2
    Best in class thinking tool
  • 0
    Orthogonality
  • 0
    Predictable
CONS OF HASKELL
  • 7
    Too much distraction in language extensions
  • 7
    Error messages can be very confusing
  • 4
    Libraries have poor documentation
  • 3
    No best practices
  • 3
    No good ABI
  • 2
    Sometimes performance is unpredictable
  • 2
    Poor packaging for apps written in it for Linux distros
  • 1
    Slow compilation

related Haskell posts

Vadim Bakaev
Shared insights
on
HaskellHaskellScalaScala

Why I am using Haskell in my free time?

I have 3 reasons for it. I am looking for:

Fun.

Improve functional programming skill.

Improve problem-solving skill.

Laziness and mathematical abstractions behind Haskell makes it a wonderful language.

It is Pure functional, it helps me to write better Scala code.

Highly expressive language gives elegant ways to solve coding puzzle.

See more
Svelte logo

Svelte

918
1K
439
A UI framework that compiles into tiny standalone JavaScript modules
918
1K
+ 1
439
PROS OF SVELTE
  • 48
    Performance
  • 34
    Reactivity
  • 31
    Javascript compiler (do that browsers don't have to)
  • 31
    Components
  • 30
    Simplicity
  • 28
    Lightweight
  • 25
    Real Reactivity
  • 25
    Fast as vanilajs
  • 24
    Near to no learning curve
  • 17
    All in one
  • 17
    Compiler based
  • 16
    Use existing js libraries
  • 15
    Scalable
  • 14
    SSR
  • 13
    Very easy for beginners
  • 12
    Composable
  • 11
    Ease of use
  • 11
    No runtime overhead
  • 9
    Built in store
  • 8
    Typescript
  • 6
    Start with pure html + css
  • 6
    Best Developer Experience
  • 5
    Templates
  • 3
    Speed
CONS OF SVELTE
  • 3
    Event Listener Overload
  • 2
    Little to no libraries
  • 2
    Complex
  • 2
    Learning Curve
  • 2
    Hard to learn

related Svelte posts

Sarmad Chaudhary
Founder & CEO at Ebiz Ltd. · | 9 upvotes · 523.3K views

Hi there!

I just want to have a simple poll/vote...

If you guys need a UI/Component Library for React, Vue.js, or AngularJS, which type of library would you prefer between:

1 ) A single maintained cross-framework library that is 100% compatible and can be integrated with any popular framework like Vue, React, Angular 2, Svelte, etc.

2) A native framework-specific library developed to work only on target framework like ElementUI for Vue, Ant Design for React.

Your advice would help a lot! Thanks in advance :)

See more
Elixir logo

Elixir

2.9K
2.9K
1.3K
Dynamic, functional language designed for building scalable and maintainable applications
2.9K
2.9K
+ 1
1.3K
PROS OF ELIXIR
  • 169
    Concurrency
  • 155
    Functional
  • 130
    Erlang vm
  • 110
    Great documentation
  • 103
    Great tooling
  • 84
    Immutable data structures
  • 79
    Open source
  • 76
    Pattern-matching
  • 61
    Easy to get started
  • 58
    Actor library
  • 29
    Functional with a neat syntax
  • 28
    Ruby inspired
  • 24
    Homoiconic
  • 23
    Erlang evolved
  • 21
    Beauty of Ruby, Speed of Erlang/C
  • 17
    Fault Tolerant
  • 13
    High Performance
  • 13
    Simple
  • 10
    Good lang
  • 9
    Stinkin' fast, no memory leaks, easy on the eyes
  • 9
    Doc as first class citizen
  • 9
    Pipe Operator
  • 7
    Resilient to failure
  • 6
    Fun to write
  • 5
    OTP
  • 5
    GenServer takes the guesswork out of background work
  • 4
    Fast, Concurrent with clean error messages
  • 4
    Idempotence
  • 4
    Not Swift
  • 4
    Pattern matching
  • 2
    Error isolation
  • 1
    Easy to use
  • 1
    Dynamic Typing
CONS OF ELIXIR
  • 11
    Fewer jobs for Elixir experts
  • 7
    Smaller userbase than other mainstream languages
  • 5
    Elixir's dot notation less readable ("object": 1st arg)
  • 4
    Dynamic typing
  • 1
    Difficult to understand
  • 1
    Not a lot of learning books available

related Elixir posts

Kamil Kowalski
Lead Architect at Fresha · | 28 upvotes · 1.4M views

When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

See more
Sebastian Gębski

Another major decision was to adopt Elixir and Phoenix Framework - the DX (Developer eXperience) is pretty similar to what we know from RoR, but this tech is running on the top of rock-solid Erlang platform which is powering planet-scale telecom solutions for 20+ years. So we're getting pretty much the best from both worlds: minimum friction & smart conventions that eliminate the excessive boilerplate AND highly concurrent EVM (Erlang's Virtual Machine) that makes all the scalability problems vanish. The transition was very smooth - none of Ruby developers we had decided to leave because of Elixir. What is more, we kept recruiting Ruby developers w/o any requirement regarding Elixir proficiency & we still were able to educate them internally in almost no time. Obviously Elixir comes with some more tools in the stack: Credo , Hex , AppSignal (required to properly monitor BEAM apps).

See more
JavaScript logo

JavaScript

253.6K
199.5K
7.8K
Lightweight, interpreted, object-oriented language with first-class functions
253.6K
199.5K
+ 1
7.8K
PROS OF JAVASCRIPT
  • 1.6K
    Can be used on frontend/backend
  • 1.5K
    It's everywhere
  • 1.1K
    Lots of great frameworks
  • 886
    Fast
  • 735
    Light weight
  • 416
    Flexible
  • 385
    You can't get a device today that doesn't run js
  • 284
    Non-blocking i/o
  • 233
    Ubiquitousness
  • 188
    Expressive
  • 51
    Extended functionality to web pages
  • 44
    Relatively easy language
  • 42
    Executed on the client side
  • 26
    Relatively fast to the end user
  • 22
    Pure Javascript
  • 17
    Functional programming
  • 11
    Async
  • 8
    Setup is easy
  • 7
    Full-stack
  • 7
    Its everywhere
  • 7
    Because I love functions
  • 7
    JavaScript is the New PHP
  • 7
    Like it or not, JS is part of the web standard
  • 6
    Future Language of The Web
  • 6
    Can be used in backend, frontend and DB
  • 6
    Expansive community
  • 5
    Love-hate relationship
  • 5
    Everyone use it
  • 5
    Easy to hire developers
  • 5
    Evolution of C
  • 5
    Supports lambdas and closures
  • 5
    Agile, packages simple to use
  • 5
    Popularized Class-Less Architecture & Lambdas
  • 5
    For the good parts
  • 4
    Function expressions are useful for callbacks
  • 4
    No need to use PHP
  • 4
    Everywhere
  • 4
    Hard not to use
  • 4
    Promise relationship
  • 4
    Scope manipulation
  • 4
    It's fun
  • 4
    Client processing
  • 4
    Nice
  • 4
    Easy to make something
  • 4
    Can be used on frontend/backend/Mobile/create PRO Ui
  • 4
    Can be used both as frontend and backend as well
  • 4
    Photoshop has 3 JS runtimes built in
  • 4
    It let's me use Babel & Typescript
  • 4
    Client side JS uses the visitors CPU to save Server Res
  • 4
    1.6K Can be used on frontend/backend
  • 4
    Stockholm Syndrome
  • 4
    What to add
  • 4
    Clojurescript
  • 4
    Most Popular Language in the World
  • 4
    Powerful
  • 4
    Versitile
  • 4
    Easy
  • 4
    Its fun and fast
  • 3
    Only Programming language on browser
  • 3
    Because it is so simple and lightweight
  • 2
    JavaScript j.s
  • 2
    Acoperișul 0757604335
  • 1
    God
  • 0
    Easy to understand
CONS OF JAVASCRIPT
  • 21
    A constant moving target, too much churn
  • 20
    Horribly inconsistent
  • 14
    Javascript is the New PHP
  • 8
    No ability to monitor memory utilitization
  • 6
    Shows Zero output in case of ANY error
  • 5
    Can be ugly
  • 4
    Thinks strange results are better than errors
  • 2
    No GitHub
  • 1
    Slow

related JavaScript posts

Zach Holman

Oof. I have truly hated JavaScript for a long time. Like, for over twenty years now. Like, since the Clinton administration. It's always been a nightmare to deal with all of the aspects of that silly language.

But wowza, things have changed. Tooling is just way, way better. I'm primarily web-oriented, and using React and Apollo together the past few years really opened my eyes to building rich apps. And I deeply apologize for using the phrase rich apps; I don't think I've ever said such Enterprisey words before.

But yeah, things are different now. I still love Rails, and still use it for a lot of apps I build. But it's that silly rich apps phrase that's the problem. Users have way more comprehensive expectations than they did even five years ago, and the JS community does a good job at building tools and tech that tackle the problems of making heavy, complicated UI and frontend work.

Obviously there's a lot of things happening here, so just saying "JavaScript isn't terrible" might encompass a huge amount of libraries and frameworks. But if you're like me, yeah, give things another shot- I'm somehow not hating on JavaScript anymore and... gulp... I kinda love it.

See more
Conor Myhrvold
Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.8M views

How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

https://eng.uber.com/distributed-tracing/

(GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

See more