|
|
|
|
|
by w10-1
1121 days 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.) |
|
[1]: https://learn.microsoft.com/en-us/dotnet/maui/ios/cli
[2]: https://docs.avaloniaui.net/tutorials/developing-for-mobile/...