I really hope so. Last code I reviewed was full of !! and companion objects trying to emulate Java static instead of top-level consts. Even I'm still trying to figure out what idiomatic Kotlin looks like. We got a ways to go...
treechicken
The interoperability is both a blessing and a curse imo since it let us half-ass the integration by leaving a bunch of Java code unconverted. I could start refactoring everything but then my team would stop reviewing my PRs due to the diff size (and then my manager would eventually find out that I've been using up work time doing this instead of shipping features during crunch week).
I really much prefer Kotlin to Java. I just wish my team had actually had a commitment to it instead of just sorta using it with no migration plan.
This is literally how this all started for us lol. Senior wanted to try to migrate everything to Kotlin in our project. Migration never finished. Now one of our major repos is just half Kotlin half Java. Devs on our team learn Kotlin by unexpectedly encountering it when they need to touch that code.
I hope not. I'm pretty sure me and my coworkers would be at each others' throats if it were not for some form of typed JS holding our Frankenstein codebase together.
B I R D S
Oh wait you're talking about torrents...
I always love passing over the river on the yellow line
Back in middle school I wore a Woodstock shirt to school and one of my classmates came up to me and was just like, "Oh man I love Woodstock". I literally had no idea Woodstock was even a thing (I thought it was just some random words on a graphic tee). Wanted so badly to just tell him that I only got it because I thought the bird on the guitar looked cool but ended up getting tongue tied :,)
Congrats! Game looks really cool! Best of luck
I liked being 16. Mature enough to design grand plans. Naive enough to actually try them.
Plus the greatest adversary I face for the rest of my life would just be standardized testing :P