4 ms·
Someone should invent a mobile platform where you can just write apps in natively compiled C/C++/ObjC. You know, kind of like the old Palm, WebOS, or iPhone pl
by musicale 7y ago
Someone should invent a mobile platform where you can just write apps in natively compiled C/C++/ObjC.
You know, kind of like the old Palm, WebOS, or iPhone platforms.
- pixelrevision 7y agoThis is still a perfectly valid thing to do on iOS
- snazz 7y agoIt's technically possible to write an entire iOS app in straight C, although it's not advised: https://stackoverflow.com/questions/10289890/how-to-write-ios-app-purely-in-c https://stackoverflow.com/questions/10289890/how-to-write-io...
- flukus 7y agoThat's basically the Librem 5 (https://puri.sm/products/librem-5/ https://puri.sm/products/librem-5/) and to me the most exciting thing about it.
- gridlockd 7y agoThe sad part is that since mobile development has now drifted so far away from that ideal, porting existing iOS/Android applications to the Librem isn't trivial. You could of course have an Android runtime on the Librem...
- flukus 7y agoThat's a good fallback for everyone's $ANDROID_APP that can't live without. But for the most part I'd be fine with not having that tire fire ported anyway, those apps are likely to be slow, suck battery and not conform at all to the native look and feel.
- harry8 7y agoNokia N900 was a beautiful thing. So beautiful it had to be killed.
- DagAgren 7y agoiOS still exists.
- gridlockd 7y agoYes, but iOS requires you to use Objective-C (or Swift) just like Android requires you to use Java. I know the comment put Objective-C right next to C and C++, but it doesn't belong there. All platforms should have (at least) C interfaces, not requiring C++ or even Objective-C.
- DagAgren 7y agoIt doesn't. You can access all Objective-C features from C, it's just a bit of a pain. There is a C interface to the Objective-C runtime.
- gridlockd 7y agoThey're still Objective-C APIs. There's a C interface to the Java runtime as well. The point is that it shouldn't be a pain to use these interfaces from C, concepts from ObjC/Java/C++ shouldn't leak into them.
- DagAgren 7y agoThat would mean either implementing your entire API twice, or adding layers of pointless indirection, for extremely little gain. It is just not reasonable.
- gridlockd 7y agoYou're assuming that people want to program applications in "platform languages" like Objective-C or Swift or Java or Kotlin. That's generally not true. They want to use their language of choice. That's why C interfaces are the reasonable choice, you can interface with them conveniently from pretty much any language and if you want a more idiomatic "pointless layer of indirection", you can build it.