Using a language on Windows that is intended for writing software for Apple products is as ridiculous as using C# on macOS.
Unity entered the chat
Swift on Windows
201–209 of 209 posts
Re: Swift on Windows
#202Earlier quoted context omitted.
SwiftUI being closed source is a huge issue for developers. Apple behaves as if every user is immediately on the latest version but the reality is the _lucky_ developers support one major version back. SwiftUI is broken in completely different ways for each minor release of iOS 13 and none of the fixes in 14 are possible to use in 13. It's shocking how mismanaged the SDK development at Apple is.
> Apple behaves as if every user is immediately on the latest version iOS 14 Adoption Surpasses 25% Across iPhone and iPad Five Days After Release https://old.reddit.com/r/apple/comments/ix3gve/ios_14_adopti... How long does it usually take on Android?
Re: Swift on Windows
#203Earlier quoted context omitted.
It enables a lot more customization and complex effects precisely because it draws every pixel itself.
Thats not necessarily to its benefit.
Re: Swift on Windows
#204Earlier quoted context omitted.
Unity entered the chat
Unity is designed to be cross platform. Let me know when you develop a real macOS desktop application in C#.
FYI -- You may want to take your head out of your ass.
Re: Swift on Windows
#205Earlier quoted context omitted.
Swift manages to be technically open-source while not really being true to the idea of open-source. To me, it always seems as if somebody at Apple saw that companies like Microsoft going open source was good publicity and decided that they should do it now too, without really understanding what "open source" means. Some examples of this IMHO include: - While Swift itself is open-source, "Foundation" (which is somethi…
> Meanwhile long-standing proposals like properly fixing generics ("Generics Manifesto") are being pushed back indefinitely Which parts of the generics manifesto are "properly fixing generics" in your opinion?
Also, there are some annoying restrictions around existentials, and documentation of Generics and other advanced type machinery could be a lot better in general.
Re: Swift on Windows
#206Earlier quoted context omitted.
> They have to prioritize resources Hence pjmlp wrote: "Poor Apple, budget cuts have been hit really hard". I think that's entirely fair. Apple's resource is not infinite, but it's certainly more than enough to port Swift to Windows. Hence pjmlp says it shows "how important this is to Apple", especially in comparison to Java (Oracle) or .NET (Microsoft). I tend to agree.
Why should Apple port Swift to Windows if it’s not going to use it? To me that sounds like the worst use of resources possible.
As for why, Microsoft apparently has enough money to port Java to Apple Silicon.
https://appleinsider.com/articles/20/09/22/microsoft-contrib...
Re: Swift on Windows
#207Earlier quoted context omitted.
I suppose if Swift can only interoperate with C APIs, Win32 would be the only option.
Well, Swift uses LLVM, so it's possible to link it to C++ code with extern "C" declarations.
The C ABI is stable. Any (normal) C compiler and a bunch of compilers of other languages can produce blobs which can be linked with each other, and by extension with C++ code with extern "C" declarations.
Re: Swift on Windows
#208Earlier quoted context omitted.
Nobody was talking about Android. And the number of people still on 12 is significant.
> Nobody was talking about Android. It matters in the current context. Developers have a much easier time targeting the latest and hottest on iOS, compared to the only other alternative. > And the number of people still on 12 is significant. Not for long if 14 is already 25% in less than a week , and most users upgrade to the latest versions soon enough.
As mentioned above this is not true. On Android developers can ship the latest and greatest to devices 4-5 years old because the first party libraries are distributed in such a way to enable that.
SwiftUI/Combine are bundled with OS versions.
Re: Swift on Windows
#209Earlier quoted context omitted.
Why should Apple port Swift to Windows if it’s not going to use it? To me that sounds like the worst use of resources possible.
I thought they have enough money for getting said resources. As for why, Microsoft apparently has enough money to port Java to Apple Silicon. https://appleinsider.com/articles/20/09/22/microsoft-contrib...