3 ms·
The Swift compiler and standard library are pretty tightly linked. The Swift type system is getting pretty complicated already, handling a whole range of lifet
by w10-1 3y ago
The Swift compiler and standard library are pretty tightly linked. The Swift type system is getting pretty complicated already, handling a whole range of lifetimes, async, the combination of protocols, generics, existentials, etc. with some magic handling for arrays and maps in the library. So the cost of cross-platform effort would be significant.
The greatest barrier to entry is XCode. It's archaic, impossible to extend, and has a very wide surface that would overwhelm any development team.
(Java works fine on macOS, but developers want to deploy to iOS.)
- delta_p_delta_x 3y ago.NET MAUI[1] and AvaloniaUI[2] run on iOS pretty well, and one can use Rider/VS Code/other editors to develop apps. [1]: https://learn.microsoft.com/en-us/dotnet/maui/ios/cli https://learn.microsoft.com/en-us/dotnet/maui/ios/cli [2]: https://docs.avaloniaui.net/tutorials/developing-for-mobile/ios/build-and-run-your-application-on-a-simulator https://docs.avaloniaui.net/tutorials/developing-for-mobile/...
- scns 3y agoHope this keeps getting investment and support by Microsoft. Choice and competition are very welcome, even though i code neither iPhone Apps nor C# ATM.
- ohgodplsno 3y agoKotlin/Native deploys and works on iOS, but due to Apple holding back on opening up Swift, it has to do everything through ObjC interop. But make no mistake, to Apple, that's a feature: if other languages have a hard time integrating in their ecosystem, they'll go away.