|about 3 years ago||5 days ago|
|MIT License||GNU General Public License v3.0 or later|
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
We haven't tracked posts mentioning FutureKit yet.
Tracking mentions began in Dec 2020.
Xcode double segue
2 projects | reddit.com/r/swift | 14 Jan 2022
I do this with RxSwift and my CLE library. Using those you can do something like this:
Anyone have a clever way of using third party packages in Swift Playgrounds?
1 project | reddit.com/r/swift | 9 Jul 2021
I've tried going to RxSwift's source and copying the RxSwift folder into my playground file's Source folder but no dice, it complains about a source file not being found. I tried flattening all the files into one folder and had the same problem.
DispatchGroup in Swift
2 projects | dev.to | 6 Mar 2021
We have defined what async code is, and two basic issues we could have when working with it: running tasks serially and in parallel. For running tasks in parallel we saw that DispatchGroup can be a simple solution for that. I will recommend using a library for this though. What I taught you here is basic async knowledge, but in real world scenarios, this won't be this straightforward, so using a battle tested library is always an advantage when working in production. I personally recommend using Apple's Combine if you can (it is supported in iOS 13 and above) or using RxSwift otherwise Finally, I can't finish this article without mentioning async-await. With async-await, probably all of this discussion will be a thing of the past. It lets us write async code that can be written like sync code. You can see the proposal (already implemented and that will be released in the next version of swift) here, and even try it in your code following a tutorial like this one.
RxSwift - easy, yet not obvious, tips
1 project | dev.to | 21 Jan 2021
I think this is the most important thing to understand with all your heart. All subjects, relays and operators might seem scary, especially with Rx-hermetic jargon. But simplifying it in your head to a simple collection will help you to understand all concepts easily. For me it was a sudden click. If you want to learn more, official docs are great source and emphasize this concept: https://github.com/ReactiveX/RxSwift/blob/main/Documentation/GettingStarted.md#observables-aka-sequences
What are some alternatives?
ReSwift - Unidirectional Data Flow in Swift - Inspired by Redux
PromiseKit - Promises for Swift & ObjC.
Bond - A Swift binding framework
ReactiveSwift - Streams of values over time
ReactiveKit - A Swift Reactive Programming Kit
ReactiveCocoa - Cocoa framework and Obj-C dynamism bindings for ReactiveSwift.
SwiftEventBus - A publish/subscribe EventBus optimized for iOS
OpenCombine - Open source implementation of Apple's Combine framework for processing values over time.
ReactorKit - A library for reactive and unidirectional Swift applications
BrightFutures - Write great asynchronous code in Swift using futures and promises
RxAlamofire - RxSwift wrapper around the elegant HTTP networking in Swift Alamofire