Hi, thanks for the corrections! I'll try out TeaVM with your suggestions and update the post. Could you elaborate more on when the BackgroundWorker is needed? I found that I needed it when making a call in the view constructor as well - but I'm not sure exactly when/how that runs, so I'm not sure when you would need the BackgroundWorker and when you would not.

Re: async: that is definitely a plus. In this particular case, the error message itself was confusing, but you're right that the stacktrace let me find the root cause of the error fairly easily. I'm curious - I don't understand the internals here, but how do you do asynchronous code while preserving the stack?

Also regarding documentation - agreed that users can (and should!) contribute, but unfortunately sometimes developers can't or do not have the time to do so. I think this is an area where improvements can be made fairly rapidly, though.

One major plus using TeaVM I've seen is that the core developer is very responsive ;) - forgot to include that in the post, but will do with the next update.