programming languages

Rank

C vs Groovy

  1. This language is suitable for real-time applications

    93% 7%
    C 61 out of 65 picked C over Groovy Groovy
  2. Programs written in this language tend to be efficient

    92% 8%
    C 76 out of 82 picked C over Groovy Groovy
  3. Writing code in this language is a lot of work

    91% 9%
    C 80 out of 87 picked C over Groovy Groovy
  4. I learned this language early in my career as a programmer

    91% 9%
    C 33 out of 36 picked C over Groovy Groovy
  5. This is a low level language

    89% 11%
    C 80 out of 89 picked C over Groovy Groovy
  6. This language is likely to be around for a very long time

    87% 13%
    C 58 out of 66 picked C over Groovy Groovy
  7. This is a mainstream language

    85% 15%
    C 30 out of 35 picked C over Groovy Groovy
  8. I use many applications written in this language

    84% 16%
    C 72 out of 85 picked C over Groovy Groovy
  9. 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 22 out of 26 picked C over Groovy Groovy
  10. Code written in this language tends to be verbose

    83% 17%
    C 77 out of 92 picked C over Groovy Groovy
  11. I would use this language for writing programs for an embedded hardware platform

    83% 17%
    C 54 out of 65 picked C over Groovy Groovy
  12. I would use this language for writing embedded programs

    80% 20%
    C 17 out of 21 picked C over Groovy Groovy
  13. This language is good for scientific computing

    79% 21%
    C 65 out of 82 picked C over Groovy Groovy
  14. This language allows me to write programs where I know exactly what they are doing under the hood

    78% 22%
    C 60 out of 76 picked C over Groovy Groovy
  15. This language has a strong static type system

    77% 23%
    C 73 out of 94 picked C over Groovy Groovy
  16. I would recommend most programmers learn this language, regardless of whether they have a specific need for it

    76% 24%
    C 38 out of 50 picked C over Groovy Groovy
  17. This language is built on a small core of orthogonal features

    75% 25%
    C 43 out of 57 picked C over Groovy Groovy
  18. This language has a high quality implementation

    74% 26%
    C 26 out of 35 picked C over Groovy Groovy
  19. This language is good for numeric computing

    74% 26%
    C 46 out of 62 picked C over Groovy Groovy
  20. This language makes it easy to shoot yourself in the foot

    73% 27%
    C 41 out of 56 picked C over Groovy Groovy
  21. There are many good commercial tools for this language

    73% 27%
    C 65 out of 89 picked C over Groovy Groovy
  22. There is a wide variety of open source code written in this language

    72% 28%
    C 59 out of 81 picked C over Groovy Groovy
  23. This language is minimal

    72% 28%
    C 45 out of 62 picked C over Groovy Groovy
  24. There is a lot of accidental complexity when writing code in this language

    71% 29%
    C 52 out of 73 picked C over Groovy Groovy
  25. Programs written in this language will usually work in future versions of the language

    69% 31%
    C 51 out of 73 picked C over Groovy Groovy
  26. I know many other people who use this language

    69% 31%
    C 60 out of 86 picked C over Groovy Groovy
  27. Developers who primarily use this language often burn out after a few years

    68% 32%
    C 35 out of 51 picked C over Groovy Groovy
  28. It's unusual for me to discover unfamiliar features

    67% 33%
    C 50 out of 74 picked C over Groovy Groovy
  29. This language is frequently used for applications it isn't suitable for

    66% 34%
    C 40 out of 60 picked C over Groovy Groovy
  30. This language is unusually bad for beginners

    66% 34%
    C 59 out of 89 picked C over Groovy Groovy
  31. This language has a very coherent design

    64% 36%
    C 37 out of 57 picked C over Groovy Groovy
  32. The resources for learning this language are of high quality

    64% 36%
    C 55 out of 85 picked C over Groovy Groovy
  33. I would use this language for mobile applications

    63% 37%
    C 45 out of 71 picked C over Groovy Groovy
  34. Learning this language improved my ability as a programmer

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

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

    61% 39%
    C 37 out of 60 picked C over Groovy Groovy
  37. This language is well documented

    60% 40%
    C 39 out of 64 picked C over Groovy Groovy
  38. Code written in this language tends to be very reliable

    60% 40%
    C 45 out of 75 picked C over Groovy Groovy
  39. I find it easy to write efficient code in this language

    59% 41%
    C 56 out of 94 picked C over Groovy Groovy
  40. The thought that I may still be using this language in twenty years time fills me with dread

    59% 41%
    C 44 out of 74 picked C over Groovy Groovy
  41. This language has a very dogmatic community

    58% 42%
    C 44 out of 75 picked C over Groovy Groovy
  42. I often get angry when writing code in this language

    58% 42%
    C 14 out of 24 picked C over Groovy Groovy
  43. This language has a very rigid idea of how things should be done

    58% 42%
    C 43 out of 74 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

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

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

    55% 45%
    C 19 out of 34 picked C over Groovy Groovy
  47. I know this language well

    55% 45%
    C 413 out of 745 picked C over Groovy Groovy
  48. Libraries in this language tend to be well documented.

    55% 45%
    C 16 out of 29 picked C over Groovy Groovy
  49. I would use this language to write a command-line app

    54% 46%
    C 42 out of 77 picked C over Groovy Groovy
  50. This language is good for beginners

    53% 47%
    C 50 out of 93 picked C over Groovy Groovy
  51. If this language didn't exist, I would have trouble finding a satisfactory replacement

    53% 47%
    C 36 out of 67 picked C over Groovy Groovy
  52. Programs written in this language tend to play well with others

    53% 47%
    C 37 out of 69 picked C over Groovy Groovy
  53. I would list this language on my resume

    52% 48%
    C 38 out of 72 picked C over Groovy Groovy
  54. This language has an annoying syntax

    51% 49%
    C 15 out of 29 picked C over Groovy Groovy
  55. I am sometimes embarrassed to admit to my peers that I know this language

    50% 50%
    C 32 out of 63 picked C over Groovy Groovy
  56. This language is likely to have a strong influence on future languages

    50% 50%
    C 39 out of 78 each for Groovy and C Groovy
  57. There are many good open-source tools for this language

    50% 50%
    C 39 out of 78 each for Groovy and C Groovy
  58. When I run into problems my colleagues can provide me with immediate help with this language

    50% 50%
    C 38 out of 76 each for Groovy and C Groovy
  59. This language has a niche in which it is great

    50% 50%
    C 34 out of 68 each for Groovy and C Groovy
  60. This language is best for very large projects

    49% 51%
    C 43 out of 85 picked Groovy over C Groovy
  61. If my code in this language successfully compiles, there is a good chance my code is correct.

    48% 52%
    C 16 out of 31 picked Groovy over C Groovy
  62. This language matches it's problem domain particularly well.

    48% 52%
    C 13 out of 25 picked Groovy over C Groovy
  63. I usually use this language on solo projects

    47% 53%
    C 47 out of 89 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 41 out of 77 picked Groovy over C Groovy
  65. It is easy to debug programs written in this language when it goes wrong

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

    42% 58%
    C 45 out of 78 picked Groovy over C Groovy
  67. This language has a good community

    41% 59%
    C 46 out of 79 picked Groovy over C Groovy
  68. I enjoy playing with this language but would never use it for "real code"

    41% 59%
    C 46 out of 78 picked Groovy over C Groovy
  69. I use this language out of choice

    40% 60%
    C 40 out of 67 picked Groovy over C Groovy
  70. This language has a niche outside of which I would not use it

    40% 60%
    C 43 out of 72 picked Groovy over C Groovy
  71. This language has unusual features that I often miss when using other languages

    40% 60%
    C 39 out of 65 picked Groovy over C Groovy
  72. I am reluctant to admit to knowing this language

    40% 60%
    C 33 out of 55 picked Groovy over C Groovy
  73. I regularly use this language

    39% 61%
    C 53 out of 87 picked Groovy over C Groovy
  74. I would use this language for writing server programs

    39% 61%
    C 50 out of 82 picked Groovy over C Groovy
  75. Code written in this language tends to be terse

    37% 63%
    C 47 out of 75 picked Groovy over C Groovy
  76. It is easy to tell at a glance what code in this language does

    37% 63%
    C 59 out of 94 picked Groovy over C Groovy
  77. This language encourages writing reusable code.

    37% 63%
    C 17 out of 27 picked Groovy over C Groovy
  78. This language excels at concurrency

    36% 64%
    C 55 out of 87 picked Groovy over C Groovy
  79. I often feel like I am not smart enough to write this language

    36% 64%
    C 19 out of 30 picked Groovy over C Groovy
  80. I usually use this language on projects with many other members

    36% 64%
    C 53 out of 83 picked Groovy over C Groovy
  81. This language is large

    35% 65%
    C 45 out of 70 picked Groovy over C Groovy
  82. When I write code in this language I can be very sure it is correct

    35% 65%
    C 49 out of 76 picked Groovy over C Groovy
  83. This language has well-organized libraries with consistent, carefully thought-out interfaces

    34% 66%
    C 42 out of 64 picked Groovy over C Groovy
  84. This language has many features which feel "tacked on"

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

    32% 68%
    C 48 out of 71 picked Groovy over C Groovy
  86. I enjoy using this language

    32% 68%
    C 65 out of 96 picked Groovy over C Groovy
  87. I can imagine using this language in my day job

    31% 69%
    C 62 out of 91 picked Groovy over C Groovy
  88. This language is easier to use for it's problem domain by removing unneeded expressiveness (such as not being Turing complete).

    30% 70%
    C 9 out of 13 picked Groovy over C Groovy
  89. This language has a good library distribution mechanism.

    30% 70%
    C 25 out of 36 picked Groovy over C Groovy
  90. Code written in this language will usually run in all the major implementations if it runs in one of them.

    30% 70%
    C 21 out of 30 picked Groovy over C Groovy
  91. I still discover new features of this language on a fairly regular basis

    29% 71%
    C 43 out of 61 picked Groovy over C Groovy
  92. I would like to write more of this language than I currently do

    29% 71%
    C 58 out of 82 picked Groovy over C Groovy
  93. I find code written in this language very elegant

    29% 71%
    C 75 out of 106 picked Groovy over C Groovy
  94. This language would be good for teaching children to write software

    28% 72%
    C 20 out of 28 picked Groovy over C Groovy
  95. This language is best for very small projects

    28% 72%
    C 54 out of 75 picked Groovy over C Groovy
  96. I rarely have difficulty abstracting patterns I find in my code

    25% 75%
    C 57 out of 77 picked Groovy over C Groovy
  97. This language encourages writing code that is easy to maintain.

    25% 75%
    C 20 out of 27 picked Groovy over C Groovy
  98. I often write things in this language with the intent of rewriting them in something else later

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

    24% 76%
    C 59 out of 78 picked Groovy over C Groovy
  100. This language excels at symbolic manipulation

    22% 78%
    C 54 out of 70 picked Groovy over C Groovy
  101. This language is very flexible

    20% 80%
    C 61 out of 77 picked Groovy over C Groovy
  102. The semantics of this language are much different than other languages I know.

    18% 82%
    C 22 out of 27 picked Groovy over C Groovy
  103. This language is expressive

    17% 83%
    C 64 out of 78 picked Groovy over C Groovy
  104. I find this language easy to prototype in

    17% 83%
    C 62 out of 75 picked Groovy over C Groovy
  105. I would use this language for casual scripting

    15% 85%
    C 75 out of 89 picked Groovy over C Groovy
  106. Code written in this language is very readable

    15% 85%
    C 60 out of 71 picked Groovy over C Groovy
  107. This language is likely to be a passing fad

    12% 88%
    C 41 out of 47 picked Groovy over C Groovy
  108. I would use this language for a web project

    12% 88%
    C 80 out of 91 picked Groovy over C Groovy
  109. This language is well suited for an agile development approach using short iterations.

    9% 91%
    C 28 out of 31 picked Groovy over C Groovy
  110. I would use this language as a scripting language embedded inside a larger application

    9% 91%
    C 59 out of 65 picked Groovy over C Groovy
  111. This is a high level language

    7% 93%
    C 82 out of 89 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.