Thanks for naming Javalin - I had not previously heard of it and it appears quite nice.
I will say though, I vastly prefer pushing configuration out of my code and into config files/text. Things like `Javalin.create { config -> config.useVirtualThreads = true }` in my opinion should live in a config file.
But, to each their own - that's the beauty of the JVM ecosystem - lots of choice and lots of ideas.
Spring Boot pushes EVERYTHING into config. Whether annotations, or YAML files or property files or Gradle or Maven files or something else.
And those things are very very hard to debug. Java tools do not have an easy way to step through the code that gets executed due to you having an annotation in your source. Or the code paths that get executed to create beans and run code and generate entirely new classes with no source code...just by adding a dependency to your project.
For the things that really should be configuration, environment variables are perfectly fine.
I will say though, I vastly prefer pushing configuration out of my code and into config files/text. Things like `Javalin.create { config -> config.useVirtualThreads = true }` in my opinion should live in a config file.
But, to each their own - that's the beauty of the JVM ecosystem - lots of choice and lots of ideas.