Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to SafariWhen comparing Scala vs Armed Bear Common Lisp, the Slant community recommends Scala for most people. In the question“What are the best languages that run on the JVM?” Scala is ranked 3rd while Armed Bear Common Lisp is ranked 14th. The most important reason people chose Scala is:
The immutable values make it perfect for working with concurrency
Specs
Question Ranking
Pros
Pro Immutable values
The immutable values make it perfect for working with concurrency
Pro Multiparadigm
Scala supports both Functional and Object Oriented styles of programming. Beginners can learn both paradigms without having to learn a new language, and experts can switch between the two according to what best suits their needs at the time.
Pro Type inference
Scala offers type inference, which, while giving the same safety as Java's type system, allows programmers to focus on the code itself, rather than on updating type annotations.
Pro Compiles to JVM bytecode
Aside from Java itself, Scala is by far the most popular of the many JVM languages. If you're developing for Android, or a similar JVM-only platform, or otherwise need out-of-the-box cross-platform compatibility, but the performance of a compiled language, Scala is the way to go.
Pro Very good online courses
On coursera you can find great introduction to Scala by Martin Odersky.
Pro Type inference leads to a simpler syntax
Pro Expressive functional programming abstraction for reusable and safe code
Pro Can be integrated into java programs for scripting capabilities
Pro Fairly simple to learn and use
Written and interoperable with Java.
Cons
Con Can be intimidating for beginners
Scala is an industrial language. It brings functional programming to the JVM, but not with a "start small and grow the language" perspective, but rather a very powerful language for professional programmers.
Con Way too complex for beginners
Even for seasoned programmers it's a difficult language.
Con Static type system inherits cruft from Java
The type system is too complicated yet still less powerful than Haskell's.
Con The java API isn't always enough
Some of its features are made private and can't easily be modified from java.
Con Can be slow and clunky because of the java overhead
It is using java.
Java is slow.
Ergo: abcl is slow.
