I think it is because that the application framework of Google Android is JVM. And JNI is so annoying that binding Kotlin and other system-level programming language other than C++ like Rust, Zig for a Android app is so hard.
For game engine developers that works for their game targeting Android, especially for commercial mature game, you have no choice but Unity engine. And take a look at Google announce
[a donation of $250,000 to the Rust Foundation](https://www.linkedin.com/feed/update/urn:li:activity:7376353...)
but there still constraint on using Rust library for Android app.
It is Ghostty that makes me believe Zig is ready for industry, and I also want to make a game engine targeting Android and iOS first, however, JNI is really annoying and I hate Google Android. I have tried Bevy for Android and as you can see it's not the fault of game engine but Google. So, use Unity or challenge it.
Just do it, thanks Gostty!
You think there aren't outdated or terrible articles on Wikipedia? Or the internet in general?
The internet misleads you. Which is why we develop good BS detectors, and double-check information as needed. There isn't perfect information anywhere. Even official docs are often riddled with errors and inconsistencies.
Perhaps this also explains why I almost think LLMs are not helpful in engineering-level projects:
1. My project involved programming languages and APIs that iterated several levels faster than LLM could publish a book
2. I have lost faith in LLMs developing software.
An example is the famous Unity game engine, but LLM has not helped its Unity DOTS architecture (ECS mode compared with GameObject mode). Although I have a basic understanding of it, both the entities API documentation and the LLM answers are terrible. I chose Unity because I heard it is mature so I think LLMs would be helpful with so much materials. Sadly, for ECS it doesn't. So I chose Bevy, a game engine that I can understand and apply by reading documents and can solve problems without the help of LLM.
