| ▲ | zarzavat 8 hours ago |
| I don't know why anyone would want to use Apple tools if they are not developing for Apple platforms. Apple barely maintains compatibility for their own platforms, using Swift on a non-Apple platform is setting yourself up for doubule pain. |
|
| ▲ | myHNAccount123 4 hours ago | parent | next [-] |
| > Apple barely maintains compatibility for their own platforms... You're commenting on a post about an update... that they apparently don't do? What? |
| |
| ▲ | groundzeros2015 4 hours ago | parent [-] | | Why are you interpreting this comment as "never receives updates"? It takes great effort to maintain API compatibility, some things aren't improved or are implicitly deprecated. |
|
|
| ▲ | frizlab 7 hours ago | parent | prev [-] |
| That was true for Swift 2, maybe a little for Swift 3, but it has not been true since a long time now… |
| |
| ▲ | ethin 6 hours ago | parent | next [-] | | In a way it still is true. Swift works on Windows and Linux until it doesn't. It's taken until a couple years ago for other build systems to get swift support (which I suppose is the fault of said build system, but Swift taking so long to be cross-platform contributed to that), and even now it (still) doesn't quite work right. C interop is a mess requiring hacks to generate clang modules to actually get Swift to see them (and CMake for example provides no easy way of doing this, or last time I checked it didn't). Oh and Swift tends to take over the linker and compilation pipelines when you enable it, at least with CMake, because... Reasons? I honestly don't know why. It causes very weird errors when I integrated Swift code into my C++ project that were a pain to actually diagnose. I eventually got it working, but still, it wasn't simple or seamless. | |
| ▲ | hu3 6 hours ago | parent | prev [-] | | If cross platform support took so long, it's a major red flag. Plus Swift is arguably too unnecessarily complex now. And there's Rust/Zig so why use Swift for low level? | | |
|
