I am, of course, just "playing devil's advocate" here a bit. NPAPI clearly had issues and I'm not enough of an expert to say if it would have been possible to simply improve it, or whether it was truly necessary to go to a whole new model. And you can certainly argue that the other browser vendors could adopt NaCL / PNaCL. I guess they have their reasons for not doing so.
It's sad really, because "Java on the Web" has a ton of value, but Sun screwed the pooch years ago with some of their decision making, leaving us where we are now. Oh well, at least there is JWS / JNLP. Hmm... come to think of it, I wonder if the OP could just rework their app to run as a JWS app, instead of as an applet? That might make everybody happy...
Maybe that's a good place to start? Kotlin is a good language anyway.
For the sake of argument I'll accept that it's maybe difficult to compare two languages in general, but in terms of Kotlin/Scala they are extremely similar languages targeting extremely similar use cases.
Kotlin is a simpler language which is a huge benefit.
https://kotlinlang.org/docs/reference/comparison-to-scala.ht...
(If you want an actually simpler language, look at Ceylon)
I'd be very interested in how you eventually decide to update your applet to be more web friendly for current browsers, as I'd like to do the same, but know very little of modern web design.
Right now only one of mine is on GitHub : Squankum, for showing operations of single-qubit operations on input qubits, both graphically and in eigenvector form : https://github.com/jeffwass/Squankum/blob/master/README.md