What is Clojure and what are its top alternatives?
Top Alternatives to Clojure
- 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
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
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 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 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
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
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 is a statically typed programming language for the JVM, Android and the browser, 100% interoperable with Java ...
Clojure alternatives & related posts
- Static typing187
- Pattern-matching178
- Jvm177
- Scala is fun172
- Types138
- Concurrency95
- Actor library88
- Solve functional problems86
- Open source83
- Solve concurrency in a safer way80
- Functional44
- Fast24
- Generics23
- It makes me a better engineer18
- Syntactic sugar17
- Scalable13
- First-class functions10
- Type safety10
- Interactive REPL9
- Expressive8
- SBT7
- Implicit parameters6
- Case classes6
- Used by Twitter4
- JVM, OOP and Functional programming, and static typing4
- Rapid and Safe Development using Functional Programming4
- Object-oriented4
- Functional Proframming3
- Spark2
- Beautiful Code2
- Safety2
- Growing Community2
- DSL1
- Rich Static Types System and great Concurrency support1
- Naturally enforce high code quality1
- Akka Streams1
- Akka1
- Reactive Streams1
- Easy embedded DSLs1
- Mill build tool1
- Freedom to choose the right tools for a job0
- Slow compilation time11
- Multiple ropes and styles to hang your self7
- Too few developers available6
- Complicated subtyping4
- My coworkers using scala are racist against other stuff2
related Scala posts
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.
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!
- Purely-functional programming89
- Statically typed66
- Type-safe59
- Open source39
- Great community38
- Built-in concurrency30
- Composable29
- Built-in parallelism29
- Referentially transparent23
- Generics19
- Intellectual satisfaction14
- Type inference14
- If it compiles, it's correct11
- Flexible7
- Monads7
- Proposition testing with QuickCheck4
- Great type system4
- Purely-functional Programming3
- One of the most powerful languages *(see blub paradox)*3
- Highly expressive, type-safe, fast development time2
- Reliable2
- Kind system2
- Pattern matching and completeness checking2
- Better type-safe than sorry2
- Type classes2
- Great maintainability of the code2
- Fun2
- Best in class thinking tool2
- Orthogonality0
- Predictable0
- Error messages can be very confusing8
- Too much distraction in language extensions8
- Libraries have poor documentation4
- No best practices3
- No good ABI3
- Sometimes performance is unpredictable2
- Poor packaging for apps written in it for Linux distros2
- Slow compilation1
related Haskell posts
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.
Common Lisp
- Flexibility24
- High-performance21
- Comfortable: garbage collection, closures, macros, REPL17
- Stable13
- Lisp12
- Code is data7
- Can integrate with C (via CFFI)6
- Multi paradigm6
- Lisp is fun5
- Easy Setup4
- Macros4
- Parentheses3
- Purelly functional3
- Open source3
- Elegant3
- DSLs1
- Clean semantics1
- Can implement almost any feature as a library1
- CLOS/MOP1
- Powerful1
- Simple syntax1
- Best programming language1
- Will still be relevant 100 years from now1
- Still decades ahead of almost all programming languages1
- Generic functions1
- Multiple values1
- Formal specification, multiple implementations1
- Too many Parentheses4
- Standard did not evolve since 19942
- No hygienic macros1
- Small library ecosystem1
related Common Lisp posts
Elixir
- Concurrency171
- Functional158
- Erlang vm132
- Great documentation111
- Great tooling104
- Immutable data structures85
- Open source80
- Pattern-matching76
- Easy to get started61
- Actor library58
- Functional with a neat syntax31
- Ruby inspired29
- Homoiconic24
- Erlang evolved24
- Beauty of Ruby, Speed of Erlang/C22
- Fault Tolerant17
- Simple14
- High Performance13
- Good lang10
- Doc as first class citizen10
- Pipe Operator10
- Stinkin' fast, no memory leaks, easy on the eyes9
- Fun to write8
- Resilient to failure7
- OTP7
- GenServer takes the guesswork out of background work5
- Not Swift4
- Pattern matching4
- Idempotence4
- Fast, Concurrent with clean error messages4
- Easy to use3
- Error isolation2
- Dynamic Typing2
- Fewer jobs for Elixir experts11
- Smaller userbase than other mainstream languages7
- Elixir's dot notation less readable ("object": 1st arg)5
- Dynamic typing4
- Difficult to understand1
- Not a lot of learning books available1
related Elixir posts
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.
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).
Julia
- Fast Performance and Easy Experimentation24
- Designed for parallelism and distributed computation21
- Free and Open Source18
- Dynamic Type System17
- Multiple Dispatch16
- Calling C functions directly16
- Lisp-like Macros16
- Powerful Shell-like Capabilities10
- Jupyter notebook integration9
- REPL8
- String handling4
- Emojis as variable names4
- Interoperability3
- Immature library management system5
- Slow program start4
- JIT compiler is very slow3
- Poor backwards compatibility3
- Bad tooling2
- No static compilation2
related Julia posts
Erlang
- Concurrency Support60
- Real time, distributed applications60
- Fault tolerance56
- Soft real-time35
- Open source31
- Functional programming21
- Message passing20
- Immutable data15
- Works as expected13
- Facebook chat uses it at backend5
- Practical4
- Knowledgeable community4
- Bullets included3
related Erlang posts
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).
Hello everyone, I plan on building a platform that supports 100s of forums out of the box, it would give the user the ability to create forums, where other users can comment, post images, and videos (the size of videos would be limited). Each forum would have the ability to trend. I have been doing a lot of research and I have arrived at Golang and Erlang as the backend languages and PostgreSQL as the DB. Erlang would be used for the routing of chats and messages, while Go would be used to manage the forums. We would also be implementing a one on one chat system like WhatsApp chat, where users can add contacts.
Please I would like to know if the languages picked are appropriate for this project. Suggestions would be appreciated.
Golang
- High-performance538
- Simple, minimal syntax392
- Fun to write359
- Easy concurrency support via goroutines299
- Fast compilation times271
- Goroutines193
- Statically linked binaries that are simple to deploy179
- Simple compile build/run procedures150
- Backed by google136
- Great community134
- Garbage collection built-in52
- Built-in Testing45
- Excellent tools - gofmt, godoc etc43
- Elegant and concise like Python, fast like C39
- Awesome to Develop37
- Used for Docker26
- Flexible interface system25
- Deploy as executable24
- Great concurrency pattern24
- Open-source Integration20
- Easy to read17
- Fun to write and so many feature out of the box17
- Go is God16
- Its Simple and Heavy duty14
- Powerful and simple14
- Easy to deploy14
- Best language for concurrency13
- Concurrency12
- Rich standard library11
- Safe GOTOs11
- Clean code, high performance10
- Easy setup10
- Simplicity, Concurrency, Performance9
- High performance9
- Hassle free deployment8
- Single binary avoids library dependency issues8
- Simple, powerful, and great performance7
- Cross compiling7
- Used by Giants of the industry7
- Gofmt6
- Garbage Collection6
- Very sophisticated syntax5
- Excellent tooling5
- WYSIWYG5
- Kubernetes written on Go4
- Widely used4
- Keep it simple and stupid4
- No generics2
- Looks not fancy, but promoting pragmatic idioms1
- Operator goto1
- You waste time in plumbing code catching errors41
- Verbose25
- Packages and their path dependencies are braindead23
- Dependency management when working on multiple projects15
- Google's documentations aren't beginer friendly15
- Automatic garbage collection overheads10
- Uncommon syntax8
- Type system is lacking (no generics, etc)6
- Collection framework is lacking (list, set, map)3
- Best programming language2
related Golang posts
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
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
Kotlin
- Interoperable with Java73
- Functional Programming support55
- Null Safety50
- Official Android support46
- Backed by JetBrains44
- Concise37
- Modern Multiplatform Applications36
- Expressive Syntax28
- Target to JVM27
- Coroutines26
- Open Source24
- Statically Typed19
- Practical elegance19
- Type Inference17
- Android support17
- Readable code14
- Powerful as Scala, simple as Python, plus coroutines <313
- Better Java12
- Pragmatic10
- Lambda9
- Target to JavaScript8
- Expressive DSLs8
- Better language for android8
- Used for Android6
- Less boilerplate code6
- Fast Programming language5
- Less code5
- Friendly community4
- Functional Programming Language4
- Less boiler plate code4
- Official Google Support3
- Native3
- Spring2
- Latest version of Java2
- Well-compromised featured Java alternative1
- Well-compromised featured Java alternative0
- Java interop makes users write Java in Kotlin7
- Frequent use of {} keys4
- Hard to make teams adopt the Kotlin style2
- Nonullpointer Exception2
- Friendly community1
- Slow compiler1
- No boiler plate code1
related Kotlin posts
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!
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.