programming languages

Rank

C vs Groovy

  1. I learned this language early in my career as a programmer

    96% 4%
    C 27 out of 28 picked C over Groovy Groovy
  2. This language is suitable for real-time applications

    94% 6%
    C 55 out of 58 picked C over Groovy Groovy
  3. Programs written in this language tend to be efficient

    93% 7%
    C 70 out of 75 picked C over Groovy Groovy
  4. This language is likely to be around for a very long time

    91% 9%
    C 55 out of 60 picked C over Groovy Groovy
  5. Writing code in this language is a lot of work

    91% 9%
    C 74 out of 81 picked C over Groovy Groovy
  6. This is a mainstream language

    89% 11%
    C 25 out of 28 picked C over Groovy Groovy
  7. This is a low level language

    89% 11%
    C 73 out of 82 picked C over Groovy Groovy
  8. I use many applications written in this language

    85% 15%
    C 67 out of 78 picked C over Groovy Groovy
  9. Code written in this language tends to be verbose

    85% 15%
    C 71 out of 83 picked C over Groovy Groovy
  10. I use a lot of code written in this language which I really don't want to have to make changes to

    84% 16%
    C 16 out of 19 picked C over Groovy Groovy
  11. I would use this language for writing programs for an embedded hardware platform

    83% 17%
    C 51 out of 61 picked C over Groovy Groovy
  12. This language is good for scientific computing

    81% 19%
    C 60 out of 74 picked C over Groovy Groovy
  13. I would use this language for writing embedded programs

    80% 20%
    C 17 out of 21 picked C over Groovy Groovy
  14. I would recommend most programmers learn this language, regardless of whether they have a specific need for it

    79% 21%
    C 31 out of 39 picked C over Groovy Groovy
  15. This language is built on a small core of orthogonal features

    78% 22%
    C 41 out of 52 picked C over Groovy Groovy
  16. This language has a strong static type system

    78% 22%
    C 68 out of 87 picked C over Groovy Groovy
  17. This language allows me to write programs where I know exactly what they are doing under the hood

    77% 23%
    C 55 out of 71 picked C over Groovy Groovy
  18. There is a wide variety of open source code written in this language

    75% 25%
    C 56 out of 74 picked C over Groovy Groovy
  19. This language makes it easy to shoot yourself in the foot

    75% 25%
    C 33 out of 44 picked C over Groovy Groovy
  20. This language is good for numeric computing

    75% 25%
    C 42 out of 56 picked C over Groovy Groovy
  21. There are many good commercial tools for this language

    74% 26%
    C 60 out of 81 picked C over Groovy Groovy
  22. There is a lot of accidental complexity when writing code in this language

    73% 27%
    C 48 out of 65 picked C over Groovy Groovy
  23. This language is minimal

    71% 29%
    C 41 out of 57 picked C over Groovy Groovy
  24. I know many other people who use this language

    70% 30%
    C 55 out of 78 picked C over Groovy Groovy
  25. This language has a high quality implementation

    70% 30%
    C 19 out of 27 picked C over Groovy Groovy
  26. Programs written in this language will usually work in future versions of the language

    70% 30%
    C 47 out of 67 picked C over Groovy Groovy
  27. Developers who primarily use this language often burn out after a few years

    68% 32%
    C 31 out of 45 picked C over Groovy Groovy
  28. This language is frequently used for applications it isn't suitable for

    68% 32%
    C 37 out of 54 picked C over Groovy Groovy
  29. It's unusual for me to discover unfamiliar features

    66% 34%
    C 46 out of 69 picked C over Groovy Groovy
  30. This language is well documented

    66% 34%
    C 36 out of 54 picked C over Groovy Groovy
  31. This language is unusually bad for beginners

    65% 35%
    C 54 out of 82 picked C over Groovy Groovy
  32. I would use this language for mobile applications

    64% 36%
    C 42 out of 65 picked C over Groovy Groovy
  33. The resources for learning this language are of high quality

    63% 37%
    C 47 out of 74 picked C over Groovy Groovy
  34. This language has a very coherent design

    63% 37%
    C 33 out of 52 picked C over Groovy Groovy
  35. There are many good tools for this language

    62% 38%
    C 47 out of 75 picked C over Groovy Groovy
  36. I can imagine this will be a popular language in twenty years time

    61% 39%
    C 34 out of 55 picked C over Groovy Groovy
  37. Code written in this language tends to be very reliable

    61% 39%
    C 42 out of 68 picked C over Groovy Groovy
  38. The thought that I may still be using this language in twenty years time fills me with dread

    61% 39%
    C 40 out of 65 picked C over Groovy Groovy
  39. I often get angry when writing code in this language

    61% 39%
    C 8 out of 13 picked C over Groovy Groovy
  40. Learning this language improved my ability as a programmer

    61% 39%
    C 46 out of 75 picked C over Groovy Groovy
  41. I find it easy to write efficient code in this language

    61% 39%
    C 52 out of 85 picked C over Groovy Groovy
  42. Libraries in this language tend to be well documented.

    60% 40%
    C 14 out of 23 picked C over Groovy Groovy
  43. This language has a very dogmatic community

    60% 40%
    C 42 out of 70 picked C over Groovy Groovy
  44. It is too easy to write code in this language that looks like it does one thing but actually does something else

    59% 41%
    C 29 out of 49 picked C over Groovy Groovy
  45. This language has an annoying syntax

    57% 43%
    C 12 out of 21 picked C over Groovy Groovy
  46. Third-party libraries are readily available, well-documented, and of high quality

    56% 44%
    C 41 out of 73 picked C over Groovy Groovy
  47. Learning this language significantly changed how I use other languages.

    56% 44%
    C 14 out of 25 picked C over Groovy Groovy
  48. I know this language well

    55% 45%
    C 334 out of 607 picked C over Groovy Groovy
  49. If my code in this language successfully compiles, there is a good chance my code is correct.

    55% 45%
    C 11 out of 20 picked C over Groovy Groovy
  50. Programs written in this language tend to play well with others

    54% 46%
    C 34 out of 62 picked C over Groovy Groovy
  51. This language has a very rigid idea of how things should be done

    54% 46%
    C 37 out of 68 picked C over Groovy Groovy
  52. I would use this language to write a command-line app

    54% 46%
    C 40 out of 74 picked C over Groovy Groovy
  53. This language is good for beginners

    53% 47%
    C 44 out of 83 picked C over Groovy Groovy
  54. I am sometimes embarrassed to admit to my peers that I know this language

    52% 48%
    C 30 out of 57 picked C over Groovy Groovy
  55. If this language didn't exist, I would have trouble finding a satisfactory replacement

    51% 49%
    C 32 out of 62 picked C over Groovy Groovy
  56. I would list this language on my resume

    51% 49%
    C 33 out of 64 picked C over Groovy Groovy
  57. This language is best for very large projects

    51% 49%
    C 38 out of 74 picked C over Groovy Groovy
  58. This language has a niche in which it is great

    50% 50%
    C 33 out of 65 picked C over Groovy Groovy
  59. This language matches it's problem domain particularly well.

    50% 50%
    C 11 out of 22 each for Groovy and C Groovy
  60. There are many good open-source tools for this language

    50% 50%
    C 36 out of 72 each for Groovy and C Groovy
  61. This language is likely to have a strong influence on future languages

    47% 53%
    C 34 out of 65 picked Groovy over C Groovy
  62. When I run into problems my colleagues can provide me with immediate help with this language

    47% 53%
    C 36 out of 68 picked Groovy over C Groovy
  63. I usually use this language on solo projects

    46% 54%
    C 43 out of 81 picked Groovy over C Groovy
  64. This language has a wide variety of agreed-upon conventions, which are generally adhered to reasonably well, and which increase my productivity

    46% 54%
    C 38 out of 71 picked Groovy over C Groovy
  65. It is easy to debug programs written in this language when it goes wrong

    44% 56%
    C 45 out of 81 picked Groovy over C Groovy
  66. This language is good for distributed computing

    44% 56%
    C 39 out of 70 picked Groovy over C Groovy
  67. I am reluctant to admit to knowing this language

    43% 57%
    C 27 out of 48 picked Groovy over C Groovy
  68. This language has a good community

    42% 58%
    C 41 out of 71 picked Groovy over C Groovy
  69. This language has unusual features that I often miss when using other languages

    42% 58%
    C 33 out of 57 picked Groovy over C Groovy
  70. I would use this language for writing server programs

    41% 59%
    C 41 out of 70 picked Groovy over C Groovy
  71. I use this language out of choice

    41% 59%
    C 34 out of 58 picked Groovy over C Groovy
  72. This language has a niche outside of which I would not use it

    40% 60%
    C 40 out of 67 picked Groovy over C Groovy
  73. I enjoy playing with this language but would never use it for "real code"

    40% 60%
    C 43 out of 72 picked Groovy over C Groovy
  74. This language encourages writing reusable code.

    39% 61%
    C 14 out of 23 picked Groovy over C Groovy
  75. I regularly use this language

    39% 61%
    C 50 out of 82 picked Groovy over C Groovy
  76. I often feel like I am not smart enough to write this language

    37% 63%
    C 15 out of 24 picked Groovy over C Groovy
  77. This language excels at concurrency

    37% 63%
    C 51 out of 81 picked Groovy over C Groovy
  78. This language is large

    36% 64%
    C 38 out of 60 picked Groovy over C Groovy
  79. It is easy to tell at a glance what code in this language does

    36% 64%
    C 56 out of 88 picked Groovy over C Groovy
  80. Code written in this language tends to be terse

    35% 65%
    C 43 out of 67 picked Groovy over C Groovy
  81. I usually use this language on projects with many other members

    35% 65%
    C 50 out of 77 picked Groovy over C Groovy
  82. This language has many features which feel "tacked on"

    34% 66%
    C 43 out of 66 picked Groovy over C Groovy
  83. This language has well-organized libraries with consistent, carefully thought-out interfaces

    33% 67%
    C 37 out of 56 picked Groovy over C Groovy
  84. When I write code in this language I can be very sure it is correct

    33% 67%
    C 43 out of 65 picked Groovy over C Groovy
  85. This language excels at text processing

    33% 67%
    C 44 out of 66 picked Groovy over C Groovy
  86. This language is easier to use for it's problem domain by removing unneeded expressiveness (such as not being Turing complete).

    33% 67%
    C 8 out of 12 picked Groovy over C Groovy
  87. I can imagine using this language in my day job

    32% 68%
    C 58 out of 86 picked Groovy over C Groovy
  88. This language has a good library distribution mechanism.

    32% 68%
    C 19 out of 28 picked Groovy over C Groovy
  89. I still discover new features of this language on a fairly regular basis

    31% 69%
    C 34 out of 50 picked Groovy over C Groovy
  90. I enjoy using this language

    30% 70%
    C 62 out of 89 picked Groovy over C Groovy
  91. I would like to write more of this language than I currently do

    28% 72%
    C 51 out of 71 picked Groovy over C Groovy
  92. I find code written in this language very elegant

    28% 72%
    C 69 out of 96 picked Groovy over C Groovy
  93. This language is best for very small projects

    26% 74%
    C 52 out of 71 picked Groovy over C Groovy
  94. I rarely have difficulty abstracting patterns I find in my code

    26% 74%
    C 50 out of 68 picked Groovy over C Groovy
  95. This language encourages writing code that is easy to maintain.

    26% 74%
    C 17 out of 23 picked Groovy over C Groovy
  96. This language would be good for teaching children to write software

    26% 74%
    C 17 out of 23 picked Groovy over C Groovy
  97. Code written in this language will usually run in all the major implementations if it runs in one of them.

    26% 74%
    C 17 out of 23 picked Groovy over C Groovy
  98. This language excels at symbolic manipulation

    25% 75%
    C 48 out of 64 picked Groovy over C Groovy
  99. I would use this language for a desktop GUI project

    24% 76%
    C 55 out of 73 picked Groovy over C Groovy
  100. I often write things in this language with the intent of rewriting them in something else later

    24% 76%
    C 34 out of 45 picked Groovy over C Groovy
  101. This language is very flexible

    21% 79%
    C 55 out of 70 picked Groovy over C Groovy
  102. This language is expressive

    18% 82%
    C 59 out of 72 picked Groovy over C Groovy
  103. I find this language easy to prototype in

    16% 84%
    C 56 out of 67 picked Groovy over C Groovy
  104. I would use this language for casual scripting

    15% 85%
    C 69 out of 82 picked Groovy over C Groovy
  105. Code written in this language is very readable

    14% 86%
    C 54 out of 63 picked Groovy over C Groovy
  106. This language is likely to be a passing fad

    13% 87%
    C 38 out of 44 picked Groovy over C Groovy
  107. I would use this language for a web project

    13% 87%
    C 72 out of 83 picked Groovy over C Groovy
  108. The semantics of this language are much different than other languages I know.

    10% 90%
    C 17 out of 19 picked Groovy over C Groovy
  109. This is a high level language

    9% 91%
    C 70 out of 77 picked Groovy over C Groovy
  110. This language is well suited for an agile development approach using short iterations.

    8% 92%
    C 21 out of 23 picked Groovy over C Groovy
  111. I would use this language as a scripting language embedded inside a larger application

    8% 92%
    C 53 out of 58 picked Groovy over C Groovy

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 C and Groovy 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.