Wow, I am pretty much exactly of the same view (except for using Python, I really don't like Python, been burned too much by its constant problems with using system libs that only ever seem to work on "my machine" - Groovy is a lot more reliable for scripts IMO)... but I do use Kotlin sometimes, but with Java 17 likely bringing sealed classes/interfaces to Java, I am less and less excited about using Kotlin.
> When you use any Micronaut AOP Advice, it creates a subclass at compile-time to provide the AOP behaviour. This can be a problem because Kotlin classes are final by default. If the application was created with the Micronaut CLI, the Kotlin all-open plugin is configured for you to automatically change your classes to open when an AOP annotation is used. To configure it yourself, add the Around class to the list of supported annotations.
