Common Lisp

Based on 24953 responses from 2121 people, we've built up the following picture of Common Lisp

Most similar to

  1. Haskell
  2. Scheme
  3. Clojure
  4. F#
  5. O'Caml

Most dissimilar from

  1. C
  2. Java
  3. PHP
  4. Visual Basic
  5. C++

All statements

  1. This language excels at symbolic manipulation
  2. Learning this language significantly changed how I use other languages.
  3. This language is very flexible
  4. This language has unusual features that I often miss when using other languages
  5. Learning this language improved my ability as a programmer
  6. I rarely have difficulty abstracting patterns I find in my code
  7. This language is expressive
  8. This language is well suited for an agile development approach using short iterations.
  9. This language is large
  10. This is a high level language
  11. I often feel like I am not smart enough to write this language
  12. The semantics of this language are much different than other languages I know.
  13. This language encourages writing reusable code.
  14. I find code written in this language very elegant
  15. I would recommend most programmers learn this language, regardless of whether they have a specific need for it
  16. This language is likely to have a strong influence on future languages
  17. I would like to write more of this language than I currently do
  18. This language has a very dogmatic community
  19. I find this language easy to prototype in
  20. I still discover new features of this language on a fairly regular basis
  21. I enjoy using this language
  22. This language is best for very large projects
  23. Code written in this language tends to be very reliable
  24. This language encourages writing code that is easy to maintain.
  25. I use this language out of choice
  26. This language is good for scientific computing
  27. Programs written in this language will usually work in future versions of the language
  28. I would use this language for writing server programs
  29. This language is good for numeric computing
  30. I would use this language as a scripting language embedded inside a larger application
  31. This language has a high quality implementation
  32. This language is likely to be around for a very long time
  33. It is easy to debug programs written in this language when it goes wrong
  34. I enjoy playing with this language but would never use it for "real code"
  35. If this language didn't exist, I would have trouble finding a satisfactory replacement
  36. This language is well documented
  37. Code written in this language tends to be terse
  38. I would use this language for a web project
  39. This language excels at text processing
  40. I usually use this language on solo projects
  41. This language is built on a small core of orthogonal features
  42. This language has a wide variety of agreed-upon conventions, which are generally adhered to reasonably well, and which increase my productivity
  43. I would use this language for casual scripting
  44. Code written in this language is very readable
  45. I often write things in this language with the intent of rewriting them in something else later
  46. When I write code in this language I can be very sure it is correct
  47. This language has a very coherent design
  48. Programs written in this language tend to be efficient
  49. It is too easy to write code in this language that looks like it does one thing but actually does something else
  50. I would use this language for writing embedded programs
  51. If my code in this language successfully compiles, there is a good chance my code is correct.
  52. This language is unusually bad for beginners
  53. I find it easy to write efficient code in this language
  54. This language excels at concurrency
  55. The resources for learning this language are of high quality
  56. This language is good for distributed computing
  57. This language would be good for teaching children to write software
  58. It is easy to tell at a glance what code in this language does
  59. There are many good commercial tools for this language
  60. This language has a good library distribution mechanism.
  61. This language has many features which feel "tacked on"
  62. This language has well-organized libraries with consistent, carefully thought-out interfaces
  63. This language has a niche in which it is great
  64. This language has a good community
  65. I learned this language early in my career as a programmer
  66. This language matches it's problem domain particularly well.
  67. Libraries in this language tend to be well documented.
  68. I would use this language to write a command-line app
  69. This language allows me to write programs where I know exactly what they are doing under the hood
  70. This language is good for beginners
  71. I am sometimes embarrassed to admit to my peers that I know this language
  72. I can imagine using this language in my day job
  73. I can imagine this will be a popular language in twenty years time
  74. I would list this language on my resume
  75. This language is easier to use for it's problem domain by removing unneeded expressiveness (such as not being Turing complete).
  76. This language has an annoying syntax
  77. This language is best for very small projects
  78. There are many good open-source tools for this language
  79. Code written in this language will usually run in all the major implementations if it runs in one of them.
  80. This language makes it easy to shoot yourself in the foot
  81. This language is suitable for real-time applications
  82. I am reluctant to admit to knowing this language
  83. I use a lot of code written in this language which I really don't want to have to make changes to
  84. Developers who primarily use this language often burn out after a few years
  85. This language has a niche outside of which I would not use it
  86. I would use this language for a desktop GUI project
  87. I know this language well
  88. There are many good tools for this language
  89. I regularly use this language
  90. I would use this language for mobile applications
  91. This language is likely to be a passing fad
  92. There is a lot of accidental complexity when writing code in this language
  93. I would use this language for writing programs for an embedded hardware platform
  94. There is a wide variety of open source code written in this language
  95. Writing code in this language is a lot of work
  96. It's unusual for me to discover unfamiliar features
  97. This language is frequently used for applications it isn't suitable for
  98. This language has a strong static type system
  99. Third-party libraries are readily available, well-documented, and of high quality
  100. I usually use this language on projects with many other members
  101. Code written in this language tends to be verbose
  102. This is a low level language
  103. This language is minimal
  104. This is a mainstream language
  105. The thought that I may still be using this language in twenty years time fills me with dread
  106. Programs written in this language tend to play well with others
  107. When I run into problems my colleagues can provide me with immediate help with this language
  108. I often get angry when writing code in this language
  109. I use many applications written in this language
  110. I know many other people who use this language
  111. This language has a very rigid idea of how things should be done