Technically, you can compile and run the standard library on Android, but as I’ll discuss later, there is zero library support, so you can’t really do much at this point.
Of course excellent support is also provided for the rest of Apple’s fleet, which includes pads, mobile devices, watches, and TVs. In terms of cross-platform capabilities we have core language support for the three major desktop platforms: MacOS, Linux, and Windows. In fact, with the recent addition of async await which addresses concurrency at the language level, I am struggling to come up with a list of major features Swift still lacks. Swift’s standard library and Foundation provide a lot functionality right out-of-the box. I’m not going to waste your time listing all of the powerful features (generics, protocols, optionals, etc.) that you have come to know and love, but let me just say one or two things. There are a lot of important building blocks we have at our disposal in 2022, so let’s recap.Īs of this writing Swift is in version 5.6. The Swift ecosystem as I see it is composed of Swift the language, standard and core libraries (mostly from Apple at this point), proprietary libraries (also Apple, but others as well), open-source packages, and the on-line community. It may not match your own…and that’s okay:) The Swift Ecosystem In 2022 Keep that in mind as I share my vision and wish list for the Swift ecosystem.
I often finding myself using Python and it’s robust ecosystem as a model for comparison when I think about what I want from get-stuff-done language. My favorite workflow at the moment is a text editor paired with a read-evaluate-print-loop (REPL) on the command line. I love working in scripting languages like Python and R.
I come from the field of medical informatics and machine learning. Each of us looks at the field of programming through a unique lens that is shaped by our training, work experience, and areas of expertise. We, as programmers, are an eclectic bunch. Wouldn’t it be nice to write complex apps and workflows end-to-end in Swift? Today I would like to talk briefly about Swift’s current ecosystem, some of the libraries and areas of support that I think are missing, and what Swift needs to become a contender as ‘the one language to rule them all’. The process and its organization feel clunky, messy, and my brain doesn’t appreciate the constant context switching. In one of my most recent mobile apps, BG Snapshot, I utilize shell scripts for low level file system tasks, Python for data munging and machine learning (ML), C++ for approximate nearest neighbors search, and Swift for building the final iOS App.
0 kommentar(er)
