Common Lisp vs Groovy: What are the differences?
Common Lisp: The modern, multi-paradigm, high-performance, compiled, ANSI-standardized descendant of the long-running family of Lisp programming languages. 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]; Groovy: A dynamic language for the Java platform. Groovy builds upon the strengths of Java but has additional power features inspired by languages like Python, Ruby and Smalltalk. It makes modern programming features available to Java developers with almost-zero learning curve.
Common Lisp and Groovy can be primarily classified as "Languages" tools.
"Flexibility" is the primary reason why developers consider Common Lisp over the competitors, whereas "Java platform" was stated as the key factor in picking Groovy.
Groovy is an open source tool with 1.49K GitHub stars and 414 GitHub forks. Here's a link to Groovy's open source repository on GitHub.
Starbucks, Cask, and PedidosYa are some of the popular companies that use Groovy, whereas Common Lisp is used by Real Softservice, NG Informática, and Platform Project. Groovy has a broader approval, being mentioned in 79 company stacks & 73 developers stacks; compared to Common Lisp, which is listed in 5 company stacks and 3 developer stacks.
What is Common Lisp?
What is Groovy?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
Some may wonder why did we choose Grails ? Really good question :) We spent quite some time to evaluate what framework to go with and the battle was between Play Scala and Grails ( Groovy ). We have enough experience with both and, to be honest, I absolutely in love with Scala; however, the tipping point for us was the potential speed of development. Grails allows much faster development pace than Play , and as of right now this is the most important parameter. We might convert later though. Also, worth mentioning, by default Grails comes with Gradle as a build tool, so why change?