Comparison of Java and C++ (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Comparison of Java and C++" in English language version.

Last modified:

Ref.Un. Ref.Website
Global rank English rank
1st place
1st place
low place
low place
2,532nd place
1,847th place
8,507th place
8,067th place
6th place
6th place
1,901st place
1,743rd place
low place
low place
low place
low place
low place
low place
low place
low place
263rd place
259th place
1,369th place
968th place
9,249th place
6,951st place
7,079th place
5,042nd place
49th place
31st place
low place
low place
64th place
28th place
3,436th place
2,060th place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
1,235th place
855th place

archive.org (Global: 6th place; English: 6th place)

arxiv.org (Global: 49th place; English: 31st place)

azulsystems.com (Global: low place; English: low place)

boost.org (Global: low place; English: low place)

cppreference.com (Global: low place; English: low place)

en.cppreference.com

ghostarchive.org (Global: 64th place; English: 28th place)

  • Hundt, Robert (27 April 2011). "Loop Recognition in C++/Java/Go/Scala" (PDF). Stanford, California: Scala Days 2011. Archived (PDF) from the original on 9 October 2022. Retrieved 17 November 2012. Java shows a large GC component, but a good code performance. [...] We find that in regards to performance, C++ wins out by a large margin. [...] The Java version was probably the simplest to implement, but the hardest to analyze for performance. Specifically the effects around garbage collection were complicated and very hard to tune; 318 kB

gnu.org (Global: 1,901st place; English: 1,743rd place)

gcc.gnu.org

herbsutter.com (Global: low place; English: low place)

ibm.com (Global: 1,369th place; English: 968th place)

www-128.ibm.com

isocpp.org (Global: low place; English: low place)

jcp.org (Global: low place; English: low place)

microsoft.com (Global: 263rd place; English: 259th place)

msdn.microsoft.com

mreinhold.org (Global: low place; English: low place)

objectmentor.com (Global: low place; English: low place)

open-std.org (Global: 7,079th place; English: 5,042nd place)

oracle.com (Global: 2,532nd place; English: 1,847th place)

docs.oracle.com

blogs.oracle.com

download.oracle.com

scala-lang.org (Global: low place; English: low place)

days2011.scala-lang.org

  • Hundt, Robert (27 April 2011). "Loop Recognition in C++/Java/Go/Scala" (PDF). Stanford, California: Scala Days 2011. Archived (PDF) from the original on 9 October 2022. Retrieved 17 November 2012. Java shows a large GC component, but a good code performance. [...] We find that in regards to performance, C++ wins out by a large margin. [...] The Java version was probably the simplest to implement, but the hardest to analyze for performance. Specifically the effects around garbage collection were complicated and very hard to tune; 318 kB

stackoverflow.com (Global: 9,249th place; English: 6,951st place)

stroustrup.com (Global: low place; English: low place)

sun.com (Global: 8,507th place; English: 8,067th place)

java.sun.com

theserverside.com (Global: low place; English: low place)

umass.edu (Global: 3,436th place; English: 2,060th place)

people.cs.umass.edu

  • Matthew Hertz, Emery D. Berger (2005). "Quantifying the Performance of Garbage Collection vs. Explicit Memory Management" (PDF). OOPSLA 2005. Archived from the original (PDF) on 6 July 2017. Retrieved 15 March 2015. In particular, when garbage collection has five times as much memory as required, its runtime performance matches or slightly exceeds that of explicit memory management. However, garbage collection's performance degrades substantially when it must use smaller heaps. With three times as much memory, it runs 17% slower on average, and with twice as much memory, it runs 70% slower.

web.archive.org (Global: 1st place; English: 1st place)

xmpp.org (Global: low place; English: low place)

zdnet.com (Global: 1,235th place; English: 855th place)

blogs.zdnet.com