View Single Post
Old 04-10-2008, 10:22 AM   #1
astrodad
Guru
astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.astrodad ought to be getting tired of karma fortunes by now.
 
astrodad's Avatar
 
Posts: 962
Karma: 568242
Join Date: Dec 2007
Device: Kindle Oasis 3, Kindle Paperwhite 1, iPad, iPhone
Cocoa vs Python (Books vs libprs500)

OK, I'll admit that I can't make up my mind on something and I want to get your help.

I am trying to decide which language/platform I should invest in: Cocoa (Objective C) or Python.

Here's why. I love the functionality and cross-platform nature of libprs500. But I love the UI, look, and snappiness of Books. I want to help contribute to both but I know I don't have the time for it. So I need to pick one platform and go with it.

Here are my pros and cons for each:

Libprs500 (Python) Pros:

1. Lots of functionality already developed
2. Cross platform
3. Google App Engine also supportw Python
4. Great developer response (Kovid's the man)

Libprs500 (Python) cons:

1. UI elements are basic and, well, ugly.
2. Slower than Objective C
3. Steep learning curve (I'm already experiencing it)
4. Question about it's longevity

Books (Cocoa) Pros:

1. Very fast and able to access advanced features of the operating system including advanced and attractive controls (Mac Only)
2. Library management code robust and easy to understand.
3. It's for the Mac only, which I have an interest in learning anyway

Books (Cocoa) Cons:

1. Lots of PRS-500(5) functionality to be written
2. Developer (Chris) is in school and response time is limited (by his own admission and is understandable)
3. Single Platform (Mac Only)

I'm just curious what you all think. Based on some of these statements, if you had some extra time to participate in one of the two projects, which would it be and why?

TIA!
astrodad is offline   Reply With Quote