Effective Objective-C 2.0: 52 Specific Ways to Improve Your iOS and OS X Programs Matt Galloway
Publisher: Addison-Wesley

Apr 7, 2014 - Google and Apple control what apps are allowed to exist, how apps are built, what apps get promoted, and charge a 30% tax on revenues. The problem that you have Yes, Apple/Google have deeper integration (AOL never made your OS or your computer), which will delay the process, but I still agree with @zachweinberg:disqus and think open alternatives are still inevitable. Oct 22, 2010 - They did a good job. May 19, 2014 - Effective Objective-C 2.0: 52 Specific Ways to Improve Your iOS and OS X Programs (Effective Software Development Series) Write Truly Great iOS and OS X Code with Objective-C 2.0! A post on O'Reilly Digital Media We also do Android, winmobile, web 2.0, and . And if you're talented enough with Objective C, you can directly capitalize on the high costs of iPhone & iPad development and make up to $250/hour creating iOS apps for clients. OS X still has good support for Ruby, Python, Perl, C, C++, as well as Objective-C, so I don't see the lock in factor here, just the acceptance that the it's time to kick Java to the farm, to rest out it's days with COBOL. Oct 2, 2012 - To install MongoDB on your specific platform, refer to the MongoDB QuickStart. Sep 7, 2010 - Things to consider when you ask this question are: which category of app you fall into, how strongly you feel about the idea, how complex the app is, and what your marketing budget looks like. Md C:mongodblog,it throws out syntax error -missing ; before statement (shell):1.same error i got while i tried installing 2.0.7,Please help me knowing how to correct it. Here are sudo ln -s /usr/local/mongodb-osx-x86_64-2.2.0 /usr/local/mongodb If you want to test your API before using it in a client application, you can invoke your REST services straight from a browser address bar. Apps as a dedicated tool solve you problems better than generic browser. But then, as OS X took hold and Apple was able to convince developers to target their non-portable/proprietary environment, Apple's fundamental control-freak tendency took over and they put less and less energy into Java.