Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ


Choose your language

InfoQ Homepage Presentations Java vs. C Performance

Java vs. C Performance



Cliff Click takes a look at Java vs C performance. He discusses both languages' strong and weak points and the programming context surrounding language choices, which often have a much stronger impact on the business of programming than mere language choice.


Cliff Click is the CTO and Co-Founder of H2O, makers of H2O, the open source math and machine learning engine for Big Data. Cliff wrote his first compiler when he was 15 (Pascal to TRS Z-80!), although Cliff’s most famous compiler is the HotSpot Server Compiler (the Sea of Nodes IR).

About the conference

Software is Changing the World. QCon empowers software development by facilitating the spread of knowledge and innovation in the developer community. A practitioner-driven conference, QCon is designed for technical team leads, architects, engineering directors, and project managers who influence innovation in their teams.

Recorded at:

Mar 27, 2016

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Nice slide

    by Binh Nguyen,

    Your message is awaiting moderation. Thank you for participating in the discussion.


  • Java vs Java software

    by Jeff Hain,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    It's true that performances are often comparable if you have good developers,
    but in practice (observed it at large scale) having a GC can hurt performances
    (other than due to pauses), in that having to manage memory explicitly forces the
    otherwise careless devs (apparently a large majority) to:

    1) Be used not to create too many things, else they'll have much cleanup
    to do (whereas GC makes it easy to do things like "new Jungle().getBanana()",
    ending up with more memory and CPU usage.)

    2) Be used to clean up obsolete information at the technical level,
    hence at the domain level (whereas GC makes it easy to just pile up data
    in maps, and forget to remove it when obsolete, ending up with both
    memory leaks and possible bugs due to obsolete data usage.)

    When people say "Java is slow" they might actually mean "Java software is slow",
    and that's more likely to be true.

    Hope I didn't start a flamewar ;)

  • apparently this guy did not write code in quite a while

    by Dan Marinescu,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    what is this cheap politics you are doing here? are you working in sales or something? the speech is literally full of technical mediocrity at best. could give you some examples, if i had that kind of spare time

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p