4 ms·
Swift has a long road ahead for the very "low" end, i.e. replacing C or even C++. It's missing, or has extremely awkward versions (`UnsafeOMGPointer`) of variou
by wool_gather 7y ago
Swift has a long road ahead for the very "low" end, i.e. replacing C or even C++. It's missing, or has extremely awkward versions (`UnsafeOMGPointer`) of various pieces right now, [and some may never even be added][0].
[0]:https://forums.swift.org/t/bit-fields-like-in-c/34651/7 https://forums.swift.org/t/bit-fields-like-in-c/34651/7
- jamil7 7y agoYeah that makes sense, I guess in my mind I don't see it as a C or C++ replacement as with Rust. To me it fits as a slightly higher level, safe, general purpose language with pretty good performance for most tasks you throw at it. After working with it for a year I feel very productive and that I can trust my code will work if it compiles. A similar feeling to Elm or maybe Rust but yet to spend a longer time with Rust.
- wool_gather 7y agoYeah, fair, and I agree with your take; there's just this longstanding idea/goal that Swift can (or will be able to) do it all.