4 ms·
If you're writing it in Swift, you're probably doing native apps anyway. So there isn't much reason to not use the native things the platform provides.
by s73v3r_ 8y ago
If you're writing it in Swift, you're probably doing native apps anyway. So there isn't much reason to not use the native things the platform provides.
- deleted 8y ago[deleted]
- coldcode 8y agoAt our company (in one of the largest companies in the US) all of our employee related tools are iOS devices. So cross platform is unnecessary. It's not like we standardized on Palm or Windows Phone, Apple is not going anywhere and neither are we.
- deleted 8y ago[deleted]
- Yoric 8y agoWell, Apple has demonstrated more than once that they are willing to U-Turn and entirely drop core technologies. By opposition, Linuxen and Microsoft try very hard to avoid breaking applications. So, while Apple is not going anywhere, whichever technologies you're using to build your iOS apps might.
- pram 8y agoMicrosoft intentionally broke compatibility with every major release of Windows Phone though, and then ultimately killed the entire platform?
- orbitur 8y agoApple hasn't given any examples of removing APIs without a deprecation lasting at least a few years... on iOS. If it's deprecated on macOS, it's going to be around for a lot longer. They can certainly make things hellish for users trying to install your kext, but the APIs will still be there.