Instead of embracing the Java/Kotlin userspace alongside C and C++ on the NDK, with the official APIs, they try to subvert into GNU/Linux.
First of all bionic isn't glibc, secondly the Linux kernel is only a matter of convenience for Google, which they could in theory replace by something else, while keeping the Java/Kotlin and the NDK C/C++ APIs.
Which is exactly termux isn't without issues on modern Android versions, not much different than using cygwin/mingw on Windows.
This is exactly Termux's point, to subvert Android into linux cheaply. Same for MinGW or MSYS2. I want to invest as few as possible on Andriod or Windows, while still able to use them in the way that I prefer.
Mine is that the Unix environment is a preferred one, particularly on a device which is nominally a Unix derivative (Linux -> Android) but which fails to deliver in its stock incarnation.
Termux doesn't solve that problem entirely, but it does remarkably well given the underlying limitations.
Instead of embracing the Java/Kotlin userspace alongside C and C++ on the NDK, with the official APIs, they try to subvert into GNU/Linux.
First of all bionic isn't glibc, secondly the Linux kernel is only a matter of convenience for Google, which they could in theory replace by something else, while keeping the Java/Kotlin and the NDK C/C++ APIs.
Which is exactly termux isn't without issues on modern Android versions, not much different than using cygwin/mingw on Windows.