I never fully switched to Kotlin. It’s good, but not good enough. I also like the direction Java has been evolving in over the last 10 years, to the point that a JVM server is actually lighter than a Node.js server :)
Sure, Java is slowly getting most of the features and sometimes even in a better form because they control the runtime (virtual threads arguably just work). But IMO Java is still incredibly verbose, Kotlin's type system is just better and I've genuinely never come across anything that would be easier to do in Java. Even virtual threads can be used from Kotlin.
For me, Java 8 was tolerable. Also used IJ a lot and it hides Java verbosity and reduced a lot of typing. That's why I didn't really see the need to switch. For better or worse, these days I don't even open IJ and just use VSCode + AI Badger mostly to review my changes. Language matters even less.
I would never use the proposed style for Java. This is simpler and easier to understand for anyone with basic knowledge of Java. Readability is more important than fancy features:
Disclosure: I am the author of Scriptella. Recently I was investigating whether I could improve its CSV import performance, and decided to establish a baseline and compare it against existing tools.
Let me know what kind of config you are interested in and I will try to run an experiment on it. I stress test StatLite in different environments, including 256MiB Alpine VPS with a Spring Boot Java app. No OOM crashes there.
Oh very dope because StatLite was the exact one I was interested in! I also figured out some dets, so I have 3 Pi's 4 Model B - 8 GB and then another Pi that is 1st gen so its ehh. Anyways, I figured with your project I could probably merge them into a cluster/database and am considering the weak link Pi serve as just a FastAPI only and the other 3 handle these - Automation: Flux CD, OpenTofu, Ansible, Cloud-init | Certs & Secrets: Cert-Manager, External Secrets, Vault | Auth: Keycloak | Storage: Longhorn
I was thinking about using StatLite to monitor just how poorly the weak Pi affects the overall workflow of the other ones to try and figure out an optimal position for it.
Yeah, that's a great test case. I am planning my own follow-up to emulate Pi using virtualization and maybe use it for CI. Feel free to follow up on GitHub discussions if you run into issues with StatLite on Pi. I would be glad to help.
There are ways to make copy-paste ChatGPT usable with things like AI Badger. Also, ChatGPT web is unmetered, so you can do review/planning work and only delegate the actual implementation to Codex.
I am happy to see JDK versions actually becoming faster and lighter over time. Nice contrast with other platforms that seem to be moving in the opposite direction.