4 ms·
I don't particularly care, whether or not Swift ever leaves the Apple ecosystem (like ObjC). In that domain, Rust will never "win." I think that Rust is an awes
by ChrisMarshallNY 4y ago
I don't particularly care, whether or not Swift ever leaves the Apple ecosystem (like ObjC). In that domain, Rust will never "win." I think that Rust is an awesome server language, though, and I'm glad to see it gain traction. I just hope that it doesn't get trashed by a bunch of junk dependencies, written in it.
I find using apps written, using hybrid systems, or PWAs, to be quite painful (on Apple devices -and that includes that awful JS TVOS system), so I am a big proponent of real native apps.
- manmal 4y agoI think whoever „wins“, it would be necessary to have good interop at least. Currently, Rust devs are integrating core libs into native iOS apps by going the C route. All this work to make everything memory safe, and then this.
- mrtesthah 4y agoSwift-based interop would provide richer type information. See how swift-bridge takes advantage of it: https://github.com/chinedufn/swift-bridge https://github.com/chinedufn/swift-bridge
- jen20 4y agoWhich direction are you talking? If you want to link against Rust there is little choice but to use a C layer because it doesn’t have a stable ABI.
- manmal 4y agoI‘m talking Swift > Rust. TIL about the unstable ABI, thanks!
- jen20 4y agoGot it - the other way is actually fine because Swift does have a stable ABI - swift-bridge [1] allows interop in terms of high level types instead of devolving to C. [1]: https://github.com/chinedufn/swift-bridge https://github.com/chinedufn/swift-bridge
- deleted 4y ago[deleted]
- deleted 4y ago[deleted]
- incrudible 4y agoWhat is a real native app? Most operating systems have multiple graphics interfaces, ui toolkits and other abstractions with varying levels of inconsistency. They could all be driven by various languages, compiled or interpreted.
- steve1977 4y agomacOS and iOS not so much. Which is probably one of the reasons why apps for these platforms are often much better (or at least more polished) than say Windows apps.
- incrudible 4y agoIn my view, "polish" is rather orthogonal. For trivial apps that just assemble the building blocks that come out of the box, I'd agree. Otherwise, I find the "native" developer experience (XCode, Swift compiler) to be rather unpleasant. Moreover, the economics of developing "natively" limit the amount of polish you can actually justify.
- ChrisMarshallNY 4y agoThe way to deal with that, is develop (or buy|integrate) dependencies that natively implement polish and chrome. For example, a UI framework may implement good transition animations. That’s pretty typical. Write an extension to UINavigationController, or UIViewController (if you use UIKit) that implements these transitions, package it as a standalone project, and integrate it, or simply have project-specific baseline framework extensions. That’s what I do. I have a ton of these packages[0]. It’s a fair bit of work, to do it yourself, but there are package[1] and extension[2] indexes. Caveat emptor. [0] https://riftvalleysoftware.com/work/open-source-projects/ https://riftvalleysoftware.com/work/open-source-projects/ [1] https://swiftpackageindex.com/ https://swiftpackageindex.com/ [2] https://swifterswift.com/ https://swifterswift.com/