Slide 14 text
Split Objective-C and Swift APIs
going forward #2807
Correct me if I'm wrong, but maintaining both an Objective-C and Swift API for RAC is a bit of
a burden, right? Perhaps going forward it's worth thinking about slimming ReactiveCocoa
down to just support Swift. I'm sure you guys feel the pull of writing things in Swift as much as I
Obviously there's a lot of people reliant on the Objective-C APIs (myself included, for some
rather large projects) but if there's support for this idea, splitting the language support up into
separate repos/projects might be a good ﬁrst step?
What do you think?