3 ms·
Interesting post. I wonder if the major pain point was the fact that they were doing dev with a language that had nothing to do with either platform. We’re cur
by archeantus 7y ago
Interesting post. I wonder if the major pain point was the fact that they were doing dev with a language that had nothing to do with either platform.
We’re currently investigating Kotlin/native and it looks really promising. We don’t have to write stuff in a foreign language, but can repurpose our existing Kotlin code and share with iOS. This model seems promising.
Does anyone have any experience with Kotlin/native?
- PunksATawnyFill 7y ago"but can repurpose our existing Kotlin code and share with iOS" How so?
- pjmlp 7y agoC++ has lots to do with Android and iOS. On Android side, Vulkan, ML, real time audio are all only available via the NDK. Project Treble allows for Java and C++ drivers, but the large majority of them are actually written in C++. Real time audio framework, Oboe, is written in C++. The Play Games infrastructure is written in C++. On the iOS side, Metal shaders, former driver framework and the new one use C++. Objective-C++ is part of the SDK and allows for easy interoperability between Objective-C and C++. Swift and clang build on top of C++, thanks to LLVM. Finally, C++ is part of the official language list on both platforms. So contrary to urban myths, C++ has plenty to do with both platforms.
- archeantus 7y agoGood points. I guess I didn’t mean that the language wasn’t valid or supported, but rather, that it wasn’t the main first-class language of the platform.