I suspect that didn’t fit into the goal of the blog post.

I don’t think it’s meant to be a postmortem on figuring out what was going on and a solution, but more a mini white paper to point out Swift can be used on the server and has some nice benefits there.

So the exact problems with the Java implementation don’t matter past “it’s heavy and slow to start up, even though it does a good job”.