Yes, vectors is one of those cases where stack allocation has a significant advantage. This will hopefully be resolved (along with cache related issues) when value types are introduced, hopefully in Java 9.
Sadly I'm not holding my breath. For the past ten years we've been upvoting requests for value types, being told that they were not necessary because the JVM was brilliant already, then after much argument and ample proof being told that stack allocation in the JVM was a better solution, then having it delayed, finding out that the implementation didn't really work that well, etc. Sun has been pretty shit about prioritizing this issue, perhaps Oracle will be better, but it's a far shittier company than even Sun was so I'm skeptical.
It's also possible I'm jusy raging because this is a problem that has been well known for well over a decade but has been played down by the folks in charge of the JVM every time it comes up, even though it remains a real problem with the platform.
The difference is that this time you hear Doug Lea and Brian Goetz talking about this as if it's definitely going into Java 9. This time it's not coming from users but form Oracle. Also theres a JEP and a prototype by John Rose. In fact, it is mention by Oracle as one of the first features of the core platforms planned for 9. This has never been the case before.
