Still maintained?

[alexmalek]

Hey, not having any trouble, but notice the repro hasn't been very active in about a year. Conrad, this still alive from your pov? We're a fan, so just checking :). Thanks, alex

[cnstoll]

Hi Alex,

I'm glad you posted. I'm sorry for the delay in responding.

At this point there's not any active development happening on MMRecord. We are still using the library in a few projects, though not as heavily as we used to.

With the introduction and rapid rise in popularity of Swift, I think the library's future is a little in question. When Swift was announced I went as far as validating that the library worked with Swift, but haven't gone any further than that. We're not currently using MMRecord in any Swift projects.

I'm open to suggestions on what you or other frequent users of the library have for how you think it should be maintained. At this point, my personal take is that I would commit to fixing any sort of breaking changes if Apple broke something about how it uses Core Data in a future release of iOS or OS X, but at this point there are no plans for completing a 2.0.0 version or taking on a re-write in Swift.

I am very glad that the library has been helpful to you and others though. If you're going to continue to use it I can at least see what I can do to make that possible.

Thanks,

• Conrad

[alexmalek]

Hey Conrad, somehow I missed your response. We definitely plan to keep using this library - it helped us build a nice formal data layer very quickly. I'm happy to hear you plan to continuing to fix breaking changes. That is probably sufficient for our needs. It'll be at least a year before we look at swift, just given our proficiency with Obj-c :). There are a few small features we'd like out of MMRecord (e.g. semantics for server-side deletes), but we can always do a fork and roll that ourselves. Thanks, alex