You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
The lower limit of improving scalac/dotc performance is 6x for this task. I don't know if javac solves the compilation task optimally so this experiment sets just the lower limit.
I think the comparison is a bit misleading, though... even if the input provided to Scala is the same complexity as Java, the fact that Scala *can* accept more complex input put a dynamic requirement (ie more work) on Scalac which Javac doesn't have.
As an extreme example, consider a trivial compiler which only accepts one single possible Java program as input. It could "compile" it near-instantaneously, and Javac would never be able to match it.
But I really like the experimentation you're doing. It does at least feel like there is a lot of scope to improve compiler performance in scalac/dotc!
The comparison is to establish the performance gap relative to the difficulty of the task. The next question is how hard would it be to structure the compiler to scale up and down with the difficulty of an input. My hunch is that it's actually not that hard.
My hunch is less optimistic, I think. ;)
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
