Alternatives to Clojure logo

Alternatives to Clojure

Scala, Haskell, Common Lisp, Elixir, and Julia are the most popular alternatives and competitors to Clojure.
1.4K
1.2K
+ 1
1.1K

What is Clojure and what are its top alternatives?

Clojure is designed to be a general-purpose language, combining the approachability and interactive development of a scripting language with an efficient and robust infrastructure for multithreaded programming. Clojure is a compiled language - it compiles directly to JVM bytecode, yet remains completely dynamic. Clojure is a dialect of Lisp, and shares with Lisp the code-as-data philosophy and a powerful macro system.
Clojure is a tool in the Languages category of a tech stack.
Clojure is an open source tool with 9.5K GitHub stars and 1.4K GitHub forks. Here’s a link to Clojure's open source repository on GitHub

Top Alternatives to Clojure

  • Scala
    Scala

    Scala is an acronym for “Scalable Language”. This means that Scala grows with you. You can play with it by typing one-line expressions and observing the results. But you can also rely on it for large mission critical systems, as many companies, including Twitter, LinkedIn, or Intel do. To some, Scala feels like a scripting language. Its syntax is concise and low ceremony; its types get out of the way because the compiler can infer them. ...

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

  • Common Lisp
    Common Lisp

    Lisp was originally created as a practical mathematical notation for computer programs, influenced by the notation of Alonzo Church's lambda calculus. It quickly became the favored programming language for artificial intelligence (AI) research. As one of the earliest programming languages, Lisp pioneered many ideas in computer science, including tree data structures, automatic storage management, dynamic typing, conditionals, higher-order functions, recursion, and the self-hosting compiler. [source: wikipedia] ...

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

  • Julia
    Julia

    Julia is a high-level, high-performance dynamic programming language for technical computing, with syntax that is familiar to users of other technical computing environments. It provides a sophisticated compiler, distributed parallel execution, numerical accuracy, and an extensive mathematical function library. ...

  • Erlang
    Erlang

    Some of Erlang's uses are in telecoms, banking, e-commerce, computer telephony and instant messaging. Erlang's runtime system has built-in support for concurrency, distribution and fault tolerance. OTP is set of Erlang libraries and design principles providing middle-ware to develop these systems. ...

  • Golang
    Golang

    Go is expressive, concise, clean, and efficient. Its concurrency mechanisms make it easy to write programs that get the most out of multicore and networked machines, while its novel type system enables flexible and modular program construction. Go compiles quickly to machine code yet has the convenience of garbage collection and the power of run-time reflection. It's a fast, statically typed, compiled language that feels like a dynamically typed, interpreted language. ...

  • Kotlin
    Kotlin

    Kotlin is a statically typed programming language for the JVM, Android and the browser, 100% interoperable with Java ...

Clojure alternatives & related posts

Scala logo

Scala

8.4K
6.4K
1.5K
A pure-bred object-oriented language that runs on the JVM
8.4K
6.4K
+ 1
1.5K
PROS OF SCALA
  • 188
    Static typing
  • 179
    Pattern-matching
  • 177
    Jvm
  • 172
    Scala is fun
  • 138
    Types
  • 95
    Concurrency
  • 88
    Actor library
  • 86
    Solve functional problems
  • 83
    Open source
  • 80
    Solve concurrency in a safer way
  • 44
    Functional
  • 23
    Generics
  • 23
    Fast
  • 18
    It makes me a better engineer
  • 17
    Syntactic sugar
  • 13
    Scalable
  • 10
    First-class functions
  • 10
    Type safety
  • 9
    Interactive REPL
  • 8
    Expressive
  • 7
    SBT
  • 6
    Implicit parameters
  • 6
    Case classes
  • 4
    Used by Twitter
  • 4
    JVM, OOP and Functional programming, and static typing
  • 4
    Rapid and Safe Development using Functional Programming
  • 4
    Object-oriented
  • 3
    Functional Proframming
  • 2
    Spark
  • 2
    Beautiful Code
  • 2
    Safety
  • 2
    Growing Community
  • 1
    DSL
  • 1
    Rich Static Types System and great Concurrency support
  • 1
    Naturally enforce high code quality
  • 1
    Akka Streams
  • 1
    Akka
  • 1
    Reactive Streams
  • 1
    Easy embedded DSLs
  • 1
    Mill build tool
  • 0
    Freedom to choose the right tools for a job
CONS OF SCALA
  • 11
    Slow compilation time
  • 7
    Multiple ropes and styles to hang your self
  • 6
    Too few developers available
  • 4
    Complicated subtyping
  • 2
    My coworkers using scala are racist against other stuff

related Scala posts

Shared insights
on
JavaJavaScalaScalaApache SparkApache Spark

I am new to Apache Spark and Scala both. I am basically a Java developer and have around 10 years of experience in Java.

I wish to work on some Machine learning or AI tech stacks. Please assist me in the tech stack and help make a clear Road Map. Any feedback is welcome.

Technologies apart from Scala and Spark are also welcome. Please note that the tools should be relevant to Machine Learning or Artificial Intelligence.

See more
Marc Bollinger
Infra & Data Eng Manager at Thumbtack · | 5 upvotes · 506.2K views

Lumosity is home to the world's largest cognitive training database, a responsibility we take seriously. For most of the company's history, our analysis of user behavior and training data has been powered by an event stream--first a simple Node.js pub/sub app, then a heavyweight Ruby app with stronger durability. Both supported decent throughput and latency, but they lacked some major features supported by existing open-source alternatives: replaying existing messages (also lacking in most message queue-based solutions), scaling out many different readers for the same stream, the ability to leverage existing solutions for reading and writing, and possibly most importantly: the ability to hire someone externally who already had expertise.

We ultimately migrated to Kafka in early- to mid-2016, citing both industry trends in companies we'd talked to with similar durability and throughput needs, the extremely strong documentation and community. We pored over Kyle Kingsbury's Jepsen post (https://aphyr.com/posts/293-jepsen-Kafka), as well as Jay Kreps' follow-up (http://blog.empathybox.com/post/62279088548/a-few-notes-on-kafka-and-jepsen), talked at length with Confluent folks and community members, and still wound up running parallel systems for quite a long time, but ultimately, we've been very, very happy. Understanding the internals and proper levers takes some commitment, but it's taken very little maintenance once configured. Since then, the Confluent Platform community has grown and grown; we've gone from doing most development using custom Scala consumers and producers to being 60/40 Kafka Streams/Connects.

We originally looked into Storm / Heron , and we'd moved on from Redis pub/sub. Heron looks great, but we already had a programming model across services that was more akin to consuming a message consumers than required a topology of bolts, etc. Heron also had just come out while we were starting to migrate things, and the community momentum and direction of Kafka felt more substantial than the older Storm. If we were to start the process over again today, we might check out Pulsar , although the ecosystem is much younger.

To find out more, read our 2017 engineering blog post about the migration!

See more
Haskell logo

Haskell

1.1K
1.1K
496
An advanced purely-functional programming language
1.1K
1.1K
+ 1
496
PROS OF HASKELL
  • 87
    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
Common Lisp logo

Common Lisp

182
222
141
The modern, multi-paradigm, high-performance, compiled, ANSI-standardized descendant of the long-running family of Lisp programming languages
182
222
+ 1
141
PROS OF COMMON LISP
  • 24
    Flexibility
  • 21
    High-performance
  • 17
    Comfortable: garbage collection, closures, macros, REPL
  • 13
    Stable
  • 12
    Lisp
  • 7
    Code is data
  • 6
    Can integrate with C (via CFFI)
  • 6
    Multi paradigm
  • 5
    Lisp is fun
  • 4
    Easy Setup
  • 4
    Macros
  • 3
    Elegant
  • 3
    Open source
  • 2
    Parentheses
  • 2
    Purelly functional
  • 1
    DSLs
  • 1
    Generic functions
  • 1
    Still decades ahead of almost all programming languages
  • 1
    Will still be relevant 100 years from now
  • 1
    Best programming language
  • 1
    Simple syntax
  • 1
    Powerful
  • 1
    Clean semantics
  • 1
    Can implement almost any feature as a library
  • 1
    Formal specification, multiple implementations
  • 1
    Multiple values
  • 1
    CLOS/MOP
CONS OF COMMON LISP
  • 4
    Too many Parentheses
  • 2
    Standard did not evolve since 1994
  • 1
    No hygienic macros
  • 1
    Small library ecosystem

related Common Lisp posts

Shared insights
on
JavaJavaCommon LispCommon Lisp

Hello everyone! I’m interested in learning AI development, and after doing a little bit of research, I’ve learned that Common Lisp and Java are the top languages for AI. Which one should I learn? What are the differences? Are they hard to learn? If anyone can help with this, it’d be very appreciated. Thank you!

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
Julia logo

Julia

433
542
121
A high-level, high-performance dynamic programming language for technical computing
433
542
+ 1
121
PROS OF JULIA
  • 18
    Fast Performance and Easy Experimentation
  • 18
    Designed for parallelism and distributed computation
  • 14
    Free and Open Source
  • 13
    Multiple Dispatch
  • 12
    Calling C functions directly
  • 12
    Dynamic Type System
  • 12
    Lisp-like Macros
  • 8
    Powerful Shell-like Capabilities
  • 5
    REPL
  • 4
    Jupyter notebook integration
  • 2
    String handling
  • 2
    Emojis as variable names
  • 1
    Interoperability
CONS OF JULIA
  • 5
    Immature library management system
  • 4
    Slow program start
  • 3
    JIT compiler is very slow
  • 3
    Poor backwards compatibility
  • 2
    Bad tooling
  • 2
    No static compilation

related Julia posts

Erlang logo

Erlang

827
675
314
A programming language used to build massively scalable soft real-time systems with requirements on high availability
827
675
+ 1
314
PROS OF ERLANG
  • 59
    Concurrency Support
  • 59
    Real time, distributed applications
  • 55
    Fault tolerance
  • 34
    Soft real-time
  • 30
    Open source
  • 20
    Functional programming
  • 19
    Message passing
  • 14
    Immutable data
  • 12
    Works as expected
  • 4
    Facebook chat uses it at backend
  • 3
    Practical
  • 3
    Knowledgeable community
  • 2
    Bullets included
CONS OF ERLANG
    Be the first to leave a con

    related Erlang posts

    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
    Shared insights
    on
    ConsulConsulElixirElixirErlangErlang
    at

    Postmates built a tool called Bazaar that helps onboard new partners and handles several routine tasks, like nightly emails to merchants alerting them about items that are out of stock.

    Since they ran Bazaar across multiple instances, the team needed to avoid sending multiple emails to their partners by obtaining lock across multiple hosts. To solve their challenge, they created and open sourced ConsulMutEx, and an Elixir module for acquiring and releasing locks with Consul and other backends.

    It works with Consul’s KV store, as well as other backends, including ets, Erlang’s in-memory database.

    See more
    Golang logo

    Golang

    15.2K
    12.4K
    3.2K
    An open source programming language that makes it easy to build simple, reliable, and efficient software
    15.2K
    12.4K
    + 1
    3.2K
    PROS OF GOLANG
    • 530
      High-performance
    • 387
      Simple, minimal syntax
    • 354
      Fun to write
    • 295
      Easy concurrency support via goroutines
    • 267
      Fast compilation times
    • 189
      Goroutines
    • 177
      Statically linked binaries that are simple to deploy
    • 148
      Simple compile build/run procedures
    • 134
      Backed by google
    • 131
      Great community
    • 50
      Garbage collection built-in
    • 42
      Built-in Testing
    • 41
      Excellent tools - gofmt, godoc etc
    • 38
      Elegant and concise like Python, fast like C
    • 34
      Awesome to Develop
    • 25
      Used for Docker
    • 24
      Flexible interface system
    • 22
      Great concurrency pattern
    • 22
      Deploy as executable
    • 19
      Open-source Integration
    • 16
      Fun to write and so many feature out of the box
    • 15
      Easy to read
    • 14
      Its Simple and Heavy duty
    • 14
      Go is God
    • 13
      Powerful and simple
    • 13
      Easy to deploy
    • 11
      Concurrency
    • 11
      Best language for concurrency
    • 10
      Safe GOTOs
    • 10
      Rich standard library
    • 9
      Clean code, high performance
    • 9
      Easy setup
    • 8
      Simplicity, Concurrency, Performance
    • 8
      High performance
    • 8
      Hassle free deployment
    • 7
      Used by Giants of the industry
    • 7
      Single binary avoids library dependency issues
    • 6
      Cross compiling
    • 6
      Simple, powerful, and great performance
    • 5
      Excellent tooling
    • 5
      Very sophisticated syntax
    • 5
      Gofmt
    • 5
      WYSIWYG
    • 5
      Garbage Collection
    • 4
      Widely used
    • 4
      Kubernetes written on Go
    • 3
      Keep it simple and stupid
    • 1
      No generics
    • 1
      Operator goto
    CONS OF GOLANG
    • 41
      You waste time in plumbing code catching errors
    • 25
      Verbose
    • 22
      Packages and their path dependencies are braindead
    • 15
      Google's documentations aren't beginer friendly
    • 15
      Dependency management when working on multiple projects
    • 10
      Automatic garbage collection overheads
    • 8
      Uncommon syntax
    • 6
      Type system is lacking (no generics, etc)
    • 2
      Collection framework is lacking (list, set, map)

    related Golang posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 40 upvotes · 4.9M 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
    Nick Parsons
    Director of Developer Marketing at Stream · | 35 upvotes · 1.6M views

    Winds 2.0 is an open source Podcast/RSS reader developed by Stream with a core goal to enable a wide range of developers to contribute.

    We chose JavaScript because nearly every developer knows or can, at the very least, read JavaScript. With ES6 and Node.js v10.x.x, it’s become a very capable language. Async/Await is powerful and easy to use (Async/Await vs Promises). Babel allows us to experiment with next-generation JavaScript (features that are not in the official JavaScript spec yet). Yarn allows us to consistently install packages quickly (and is filled with tons of new tricks)

    We’re using JavaScript for everything – both front and backend. Most of our team is experienced with Go and Python, so Node was not an obvious choice for this app.

    Sure... there will be haters who refuse to acknowledge that there is anything remotely positive about JavaScript (there are even rants on Hacker News about Node.js); however, without writing completely in JavaScript, we would not have seen the results we did.

    #FrameworksFullStack #Languages

    See more
    Kotlin logo

    Kotlin

    10.8K
    8.3K
    565
    Statically typed Programming Language targeting JVM and JavaScript
    10.8K
    8.3K
    + 1
    565
    PROS OF KOTLIN
    • 66
      Interoperable with Java
    • 51
      Functional Programming support
    • 46
      Null Safety
    • 41
      Backed by JetBrains
    • 41
      Official Android support
    • 33
      Concise
    • 32
      Modern Multiplatform Applications
    • 25
      Expressive Syntax
    • 24
      Coroutines
    • 23
      Target to JVM
    • 22
      Open Source
    • 16
      Statically Typed
    • 16
      Practical elegance
    • 15
      Type Inference
    • 15
      Android support
    • 11
      Better Java
    • 10
      Pragmatic
    • 10
      Readable code
    • 9
      Powerful as Scala, simple as Python, plus coroutines <3
    • 7
      Lambda
    • 7
      Better language for android
    • 7
      Expressive DSLs
    • 7
      Target to JavaScript
    • 6
      Less boilerplate code
    • 5
      Used for Android
    • 4
      Less code
    • 4
      Fast Programming language
    • 3
      Functional Programming Language
    • 3
      Less boiler plate code
    • 3
      Friendly community
    • 2
      Native
    • 1
      Latest version of Java
    CONS OF KOTLIN
    • 7
      Java interop makes users write Java in Kotlin
    • 4
      Frequent use of {} keys
    • 2
      Hard to make teams adopt the Kotlin style
    • 2
      Nonullpointer Exception
    • 1
      Friendly community
    • 1
      Slow compiler
    • 1
      No boiler plate code

    related Kotlin posts

    Shivam Bhargava
    AVP - Business at VAYUZ Technologies Pvt. Ltd. · | 22 upvotes · 346.7K views

    Hi Community! Trust everyone is keeping safe. I am exploring the idea of building a #Neobank (App) with end-to-end banking capabilities. In the process of exploring this space, I have come across multiple Apps (N26, Revolut, Monese, etc) and explored their stacks in detail. The confusion remains to be the Backend Tech to be used?

    What would you go with considering all of the languages such as Node.js Java Rails Python are suggested by some person or the other. As a general trend, I have noticed the usage of Node with React on the front or Node with a combination of Kotlin and Swift. Please suggest what would be the right approach!

    See more
    Jakub Olan
    Node.js Software Engineer · | 17 upvotes · 310.8K views

    In our company we have think a lot about languages that we're willing to use, there we have considering Java, Python and C++ . All of there languages are old and well developed at fact but that's not ideology of araclx. We've choose a edge technologies such as Node.js , Rust , Kotlin and Go as our programming languages which is some kind of fun. Node.js is one of biggest trends of 2019, same for Go. We want to grow in our company with growth of languages we have choose, and probably when we would choose Java that would be almost impossible because larger languages move on today's market slower, and cannot have big changes.

    See more