Fistpump

[brynbellomy]

Dude. I was just sitting here thinking about how to put together a simple Reactive Cocoa-based FSM and had the idle thought that I probably ought to give GitHub a cursory search before banging one out from scratch. This is an awesome coincidence.

So I wanted to get in touch because I'd like to try to collaborate (fairly) actively on this. Is this just an idea you're playing around with or something you intend to develop further?

Also, while I'm on the subject, I have a few libs/CocoaPods you might be interested in -- ReactiveCocoa and FSM stuff:

• brynbellomy/GCDThreadsafe - a concrete protocol (/mixin) that adds some convenient methods + properties to any class to make threadsafety simple (has a few unit tests)
• brynbellomy/StateMachine-GCDThreadsafe - FSM that implements GCDThreadsafe concrete protocol (has decent unit tests)
• brynbellomy/ReactiveJackson - misc. ReactiveCocoa helpers and experiments (definitely no unit tests)

There are a few others up there, some ReactiveCocoaLayout stuff mixed in, etc. Anyway, let me know what you think!

[erikprice]

Interesting coincidence! I'm definitely maintaining this over the long haul; it's not just an experiment – I wrote this because I needed it. I didn't realize anyone else was interested, or I'd have been more rigorous about filing issues for its features. For example, adding a podspec is something that I know I need to do, but just haven't gotten around to yet.

However, I would love to keep the API as lean as possible, simply because I hate big things. Building on top of RACSignals makes that much easier. For example, if clients need safe access from multiple threads, they should be able to manage that using -deliverOn, rather than require it to be built into the core. Operations can be exposed as signal decorators, etc.

It would be great to have your collaboration, especially if you see something missing or any problems, or have any ideas for new functionality.