Timeline for Best way of structuring a library?
Current License: CC BY-SA 2.5
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:25 | history | edited | CommunityBot |
replaced http://stackapps.com/ with https://stackapps.com/
|
|
| Jun 2, 2010 at 22:18 | comment | added | Matt S. | ah. Now it makes sense! When I first saw you were modeling it off of Core Data I thought you were a little nuts. But now it makes perfect sense to me! I originally modeled mine off of MGTwitterEngine, but I slowly moved away from it because I wanted to make it easier to include new API features | |
| Jun 2, 2010 at 22:03 | comment | added | Dave DeLong | I modeled it off of CoreData because SO is essentially a glorified data store, and a lot of Cocoa devs are familiar with how CoreData works. It seemed to me that by mimicking it, it would help lower the barrier to adoption. The significant architectural difference is that in StackKit, you can execute requests asynchronously, which you can't do in CoreData. | |
| Jun 2, 2010 at 21:50 | history | answered | Matt S. | CC BY-SA 2.5 |