[rikf]

I agree with everything you said. Here is an interesting lwn article from when the azule people originally tried to push their change/enhancements upstream.

http://lwn.net/Articles/392307/

Seems like either the quality wasnt there or the linux people where resistant to change.

Some more info here. http://en.wikipedia.org/wiki/User:AzulPM/Managed_Runtime_Ini...

Its a pitty that this type of GC hasn't found widespread use because it gives us the best of both worlds, in terms of automatics memory management and performance.

edit for spelling mistake

[nickik]

Well I think it was not there fault and not the linux peoples fault. I have read everything I could find on this.

The linux people are write to not just exept code from outsider into there most importent subsystems like the scheduler. Azul did more of a code dumb then really try to get patches upstream. If they had taken the time to split up there code into diffrent patches and then take the time to explain why they needed it, why lots of other people also needed it, they might have gotten lot of it threw, or at least get the conversation rolling on what the linux guys could do to make managed runtimes faster.

Its of course also true that managed runtimes are not what linux kernal hackers focus on.

So it boils down to Azul guys not having enougth time to do it right and the linux people were not exited enougth to roll withit themself.

Maybe there was a lot more talk going on in the background, but I at least could not find much more on this.

[nfa_backward]

It looks like their attention has turned to LLVM.

http://www.philipreames.com/Blog/2014/06/04/code-for-late-sa...

http://www.azulsystems.com/about_us/careers/llvm-compiler-en...

[hga]

I've been following Philip Reames' blog, it's good to see LLVM get some serious precise GC love.

Reading the job advert, I would have to wonder if they want to avoid an all in, 100% bet on the Hotspot JVM, not to mention strict JVMs in general. I wouldn't be surprised if they have the best concentration of knowledge on Hotspot in the world, including Oracle, might be getting a bit tired of it, and certainly would know the limitations of its code base by now.

[nickik]

I think that they might just want to profit from all the love going into LLVM. Currenlty hotspot has costum optimization and if you have a product based on it you have to maintain this and improve it. If you manage to creat a fast powerful LLVM based JVM you can profit from the other work going into that space and maybe distance yourself from the orcale standard.

However, currently not that many JIT are LLVM based so it seams that it needs some love to get this to working well. Both for GC and compilation speed. Thats at least my guess.

[chrisseaton]

There's always Graal - OracleLabs' JVM compiler implemented in Java - for new experiments in compilation