Common Lisp vs Idris
When comparing Common Lisp vs Idris, the Slant community recommends Common Lisp for most people. In the question“What are the best (productivity-enhancing, well-designed, and concise, rather than just popular or time-tested) programming languages?” Common Lisp is ranked 4th while Idris is ranked 29th. The most important reason people chose Common Lisp is:
Almost all aspects of the language are designed with interactive/repl use in mind.
Ranked in these QuestionsQuestion Ranking
Pros
Pro Carefully designed for interactive use
Almost all aspects of the language are designed with interactive/repl use in mind.
Pro Very Powerful REPL with SLIME
SLIME (Superior Lisp Interaction Mode for Emacs).
Pro Condition/restart system
It is easy to recover from errors. Error resolution can be determined by the user at the REPL.
Pro Image based runtime
The state of the program may be saved and reloaded as an image, supporting safer modification of the running program. New code may be compiled into the image as the program runs, while late binding ensures that symbol redefinitions take effect throughout the program.
Pro Almost as fast as, or faster than, C
Some compilers such as SBCL can be faster than C or other low-level languages, and most compilers can generate fast native code.
Pro Full dependent types
Idris not only has support for type classes, but is a fully dependently typed language, giving you the full power to statically verify your code.
Pro Domain driven design and type driven development
Because of full dependent types in Idris, the programmer can focus more on modelling the domain with types and waste less time fixing common bugs that the type checker will catch. Dependent types help apply type driven development and a lot of code auto generation, making the compiler and type checker an ally in developing working software instead of just getting in the way.
Cons
Con Not widely used
Con Not widely used
Con Weaker type inference
As type inference is undecidable for dependently-typed languages, Idris cannot offer the full type inference that Haskell supports, and so more type annotations will be needed.
Con Different semantics from Haskell
Idris, while similar to Haskell, has strict semantics, which may cause some confusion if your backend is done in Haskell. If using Idris, it would make sense to do the backend in Idris as well, if not for the fact that Idris currently has fewer libraries available for web development than Haskell.
