> may require a quick look at the API docs But that tradeoff of memory footprint vs performance implemented by Oracle is not in the API documentation[1] for J

> may require a quick look at the API docs But that tradeoff of memory footprint vs performance implemented by Oracle is not in the API documentation[1] for Java 7 nor Java 8. One would have to stumble across other sources such as unofficial blogs[2] written by non-Oracle employees like Mikhail Vorontsov. That blog article then triggers an explanation from the actual coder that's buried in a reddit thread[3]. Hunting down why your business-domain java code is now suddenly slower because of hidden GC tuning is taking time away from "solving the problem." Your rebuttal consists of: -- repeating the "premature optimization" meme which is not relevant in this case. -- recommending to look at the API docs, which doesn't even have the information! [1]v7: https://docs.oracle.com/javase/7/docs/api/java/lang/String.html https://docs.oracle.com/javase/7/docs/api/java/lang/String.h... v8: https://docs.oracle.com/javase/8/docs/api/java/lang/String.html https://docs.oracle.com/javase/8/docs/api/java/lang/String.h... [2]http://java-performance.info/changes-to-string-java-1-7-0_06/ http://java-performance.info/changes-to-string-java-1-7-0_06... [3]https://www.reddit.com/comments/1qw73v https://www.reddit.com/comments/1qw73v