rawdraw

Java's bytecode is also more information dense than assembly is. Even if you only support a single architecture, a pure-Java Android app is going to almost certainly be smaller than a pure-C one, and by non-trivial amounts. If you start adding things like the Kotlin standardy library or Jetpack libraries or whatever then yes size balloons. But so too will the C app's size as its feature set expands to match. For example if this framework supported text[1] its size would explode as it grew ICU, FreeType, etc... dependencies, which are "huge." 1: yes there is a CNFGDrawText function but it uses a static map ( https://github.com/cntools/rawdraw/blob/a2a9f3c88b5caf92ef3c... ) which I'm pretty sure is ASCII only, and obviously doesn't support fonts. Or internationalization of any kind. And similarly for text layout it only "works" because it's

> A little bit of this also has to do to stick it to all those luddites people on the internet who post "that's impossible" or "you're doing it wrong" to Stack Overflow questions... > Requesting permissions in the JNI "oh you have to do that in Java" or other dumb stuff like that. > If you want a bunch of examples of how to do a ton of things in C on Android that you "need" java for, scroll to the bottom of this file: > https://github.com/cntools/rawdraw/blob/master/CNFGEGLDriver... > it shows how to use the JNI to marshall a ton of stuff to/from the Android API without needing to jump back into Java/Kotlin land. I respect this attitude but it's wrong to say Java isn't being used or executed. The truth is Java code is being called from C. jclass ClassActivity = env->FindClass(envptr, "android/app/Activity"); jmethodID MethodrequestPer

Looks to be based on https://github.com/cntools/rawdraw, "CN's Fundamental Graphics Library", though I don't know who CN is.