Future of SQLPO

[Elijah Windsor]

What's the future have in store? I've heard that the maker of SQLPO
has gone on to other things. Is there going to be another SQLPO, or
should we just migrate away from Rails?

[Hunter Hillegas]

I'm a little confused what this has to do with Rails?

I assume most people will move to Core Data for persistence.

[Ken]

Core Data seems like a logical migration, unless you want to maintain
compatibility with iPhone OS 2.x. My personal plan is to maintain
compatibility with 2.x for several months, until the majority of
people have updated to 3.0. At that time, I will begin to take
advantage of 3.0 enhancements to the SDK.

On that topic, is there any way for us as developers to see the
adoption rate of the various OS versions? If I had a way to tell how
many people were on 2.0 / 3.0, then I wouldn't have to guess about
when to switch. I know we could access the OS version in code, but I
don't want to have to send that information back to a server
somewhere. I'd just like to be able to get that information from
Apple somehow...

KM

[Hunter Hillegas]

Apple hasn't provided it in the past.

Third party analytics providers like Pinch have disclosed their stats,
which if I recall, trended heavily towards very fast adoption of new
OS versions.

[Elijah Windsor]

Ah sorry, I am coming from a Rails background and that's how I found
out about SQLPO. I'm new to developing for Apple products so Core
Data is a brand-new idea to me, but I will definitely start learning
about it.

[Andrew W. Donoho]

On Jun 1, 2009, at 12:49 PM, Elijah Windsor wrote:

> What's the future have in store? I've heard that the maker of SQLPO
> has gone on to other things. Is there going to be another SQLPO

While I think we can say there will be no new feature releases of
SQLPO, there are bug fixes. I've submitted a few to this list.

Which brings up the question: do we want a new archive that has bug
fixes rolled into it? I suspect it would be worthwhile. Do any of you
have bug fixes to share?

Andrew