> they chose to implement the scheduler in Java instead of C(++) and you're set for performance problems The JDK has historically used some native implementati

> they chose to implement the scheduler in Java instead of C(++) and you're set for performance problems The JDK has historically used some native implementations in its stdlib (zip, imageio and others), back when the runtime wasn't as fast as it is today. But today's runtime would often be faster in Java than those native implementations.