programming languages

Rank

Common Lisp vs Scheme

  1. This language is large

    91% 9%
  2. This language is best for very large projects

    79% 21%
  3. This language is well suited for an agile development approach using short iterations.

    74% 26%
  4. This language is unusually bad for beginners

    74% 26%
  5. There are many good commercial tools for this language

    71% 29%
  6. I still discover new features of this language on a fairly regular basis

    71% 29%
  7. This language has many features which feel "tacked on"

    70% 30%
  8. This language has an annoying syntax

    69% 31%
  9. I would list this language on my resume

    69% 31%
  10. I would use this language for writing server programs

    69% 31%
  11. Third-party libraries are readily available, well-documented, and of high quality

    69% 31%
  12. Programs written in this language tend to be efficient

    68% 32%
  13. This language is good for numeric computing

    67% 33%
  14. This is a mainstream language

    67% 33%
  15. This language makes it easy to shoot yourself in the foot

    66% 34%
  16. This language has a good library distribution mechanism.

    65% 35%
  17. This language is very flexible

    65% 35%
  18. This language is good for scientific computing

    64% 36%
  19. This language excels at text processing

    64% 36%
  20. This language has unusual features that I often miss when using other languages

    64% 36%
  21. This language encourages writing reusable code.

    63% 37%
  22. This language has a high quality implementation

    62% 38%
  23. I often get angry when writing code in this language

    62% 38%
  24. There is a lot of accidental complexity when writing code in this language

    62% 38%
  25. I often feel like I am not smart enough to write this language

    62% 38%
  26. I find it easy to write efficient code in this language

    61% 39%
  27. This language has a strong static type system

    61% 39%
  28. The thought that I may still be using this language in twenty years time fills me with dread

    61% 39%
  29. There are many good tools for this language

    59% 41%
  30. Programs written in this language will usually work in future versions of the language

    59% 41%
  31. It is too easy to write code in this language that looks like it does one thing but actually does something else

    59% 41%
  32. There are many good open-source tools for this language

    59% 41%
  33. There is a wide variety of open source code written in this language

    58% 42%
  34. This language has well-organized libraries with consistent, carefully thought-out interfaces

    58% 42%
  35. I would use this language for a web project

    57% 43%
  36. This language excels at symbolic manipulation

    56% 44%
  37. It is easy to debug programs written in this language when it goes wrong

    56% 44%
  38. I usually use this language on projects with many other members

    56% 44%
  39. If this language didn't exist, I would have trouble finding a satisfactory replacement

    56% 44%
  40. This language is suitable for real-time applications

    55% 45%
  41. I know many other people who use this language

    55% 45%
  42. This is a high level language

    54% 46%
  43. I rarely have difficulty abstracting patterns I find in my code

    54% 46%
  44. I can imagine using this language in my day job

    53% 47%
  45. I am reluctant to admit to knowing this language

    53% 47%
  46. Writing code in this language is a lot of work

    53% 47%
  47. Code written in this language tends to be very reliable

    53% 47%
  48. Libraries in this language tend to be well documented.

    53% 47%
  49. I use many applications written in this language

    52% 48%
  50. This is a low level language

    52% 48%
  51. This language is well documented

    52% 48%
  52. This language has a wide variety of agreed-upon conventions, which are generally adhered to reasonably well, and which increase my productivity

    52% 48%
  53. The semantics of this language are much different than other languages I know.

    52% 48%
  54. This language has a very dogmatic community

    51% 49%
  55. I learned this language early in my career as a programmer

    50% 50%
  56. This language is likely to be around for a very long time

    50% 50%
  57. I often write things in this language with the intent of rewriting them in something else later

    50% 50%
  58. This language excels at concurrency

    50% 50%
  59. This language is frequently used for applications it isn't suitable for

    50% 50%
  60. This language is expressive

    50% 50%
  61. I use this language out of choice

    50% 50%
  62. I would use this language for a desktop GUI project

    49% 51%
  63. I usually use this language on solo projects

    49% 51%
  64. I would use this language to write a command-line app

    49% 51%
  65. Developers who primarily use this language often burn out after a few years

    49% 51%
  66. I would like to write more of this language than I currently do

    49% 51%
  67. I am sometimes embarrassed to admit to my peers that I know this language

    48% 52%
  68. Code written in this language tends to be verbose

    47% 53%
  69. This language has a niche in which it is great

    46% 54%
  70. I find this language easy to prototype in

    46% 54%
  71. I enjoy using this language

    46% 54%
  72. When I run into problems my colleagues can provide me with immediate help with this language

    46% 54%
  73. This language has a niche outside of which I would not use it

    45% 55%
  74. Programs written in this language tend to play well with others

    45% 55%
  75. I regularly use this language

    45% 55%
  76. This language is good for distributed computing

    45% 55%
  77. This language allows me to write programs where I know exactly what they are doing under the hood

    44% 56%
  78. I know this language well

    44% 56%
  79. I use a lot of code written in this language which I really don't want to have to make changes to

    44% 56%
  80. Learning this language improved my ability as a programmer

    44% 56%
  81. When I write code in this language I can be very sure it is correct

    43% 57%
  82. This language has a good community

    43% 57%
  83. Code written in this language will usually run in all the major implementations if it runs in one of them.

    43% 57%
  84. This language matches it's problem domain particularly well.

    43% 57%
  85. Learning this language significantly changed how I use other languages.

    43% 57%
  86. I would use this language for casual scripting

    42% 58%
  87. I can imagine this will be a popular language in twenty years time

    42% 58%
  88. This language is likely to have a strong influence on future languages

    42% 58%
  89. This language is likely to be a passing fad

    40% 60%
  90. This language encourages writing code that is easy to maintain.

    38% 62%
  91. I would use this language for mobile applications

    37% 63%
  92. This language has a very rigid idea of how things should be done

    37% 63%
  93. Code written in this language tends to be terse

    37% 63%
  94. The resources for learning this language are of high quality

    35% 65%
  95. I would use this language for writing programs for an embedded hardware platform

    34% 66%
  96. Code written in this language is very readable

    34% 66%
  97. It is easy to tell at a glance what code in this language does

    34% 66%
  98. This language is easier to use for it's problem domain by removing unneeded expressiveness (such as not being Turing complete).

    33% 67%
  99. If my code in this language successfully compiles, there is a good chance my code is correct.

    33% 67%
  100. This language is best for very small projects

    32% 68%
  101. I enjoy playing with this language but would never use it for "real code"

    29% 71%
  102. I find code written in this language very elegant

    27% 73%
  103. I would recommend most programmers learn this language, regardless of whether they have a specific need for it

    26% 74%
  104. It's unusual for me to discover unfamiliar features

    25% 75%
  105. I would use this language as a scripting language embedded inside a larger application

    23% 77%
  106. I would use this language for writing embedded programs

    21% 79%
  107. This language is built on a small core of orthogonal features

    14% 86%
  108. This language has a very coherent design

    13% 87%
  109. This language is good for beginners

    12% 88%
  110. This language would be good for teaching children to write software

    10% 90%
  111. This language is minimal

    9% 91%

What's going on here?

The absolute rankings are interesting for large scale comparisons but when you want to know about two specific languages it's much more informative to look at how the two fare when they go directly head to head.

Here are all the statements which we've got enough comparisons between Common Lisp and Scheme to be meaningful and which of the two our users picked.

The order in which we're presenting them is a little arbitrary (sorry), but we've tried to put the things which they're both good at first so as to give you the most interesting picture of it.