Re: An idea I have: Android TTS to Windows bridge, and a problem with myse
I am not trying to cause a language debate. For the phones, you must use a first party language to create multi-language libraries or to integrate deeply with platform-specific functionality like custom TTS engines. For iOS that means Objective-C or Swift. For Android that means Java or another JVM language. That's the end of the story. You have very little choice because it's a walled garden. On desktop, to make cross-language libraries you have to use Rust, C++, C, or a number of more niche options for a different set of reasons, and again have little choice. There are very few languages that can "speak" the C ABI without huge headaches. That is also the end of that story as well.
Use C# if you want. As I said it's at least not a bad choice. But that doesn't change the fact that a lot of the sudden C# popularity is exactly what I described.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
