• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Developer Moving to Mac & Looking for Advice
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Developer Moving to Mac & Looking for Advice


  • Subject: Re: Developer Moving to Mac & Looking for Advice
  • From: Shawn Erickson <email@hidden>
  • Date: Fri, 11 Nov 2005 08:41:51 -0800


On Nov 11, 2005, at 8:15 AM, Ima Newbie wrote:

Good morning, all!

I am asking this question to the XCode group because I am looking for a generalized opinion on where to go first/next. I figure, XCode allows development with multiple languages, and is tailored to Mac, so its members probably represent the best possible group of people to ask.

My questions are as follows:

1. What is the most cost-effective way to begin developing for the Mac platform?

Not sure how to answer this not knowing what type of "cost" you are look at.


2. Based on the types of apps I am interested in, what languages / technologies should I focus on while moving to the Mac?

The main stays on Mac OS X are the following...

Cocoa & Objective-C/C++ (Python, etc. are also bridged)
Carbon & C/C++
J2SE/J2EE & Java (JNI to C/C++/etc.)

...but just about anything else is available and viable depending on what you are doing.

My background is as follows:

A. I started in VB in 1994, went to C# in 2000, and have read several books on JDK5.

B. Mostly everything I build are database-centric hybrid middleware applications (web & compiled).

C. I enjoy creating highly scalable multi-platform applications.

For server back-end I recommend Java (things like Jboss, Tomcat, etc. or WebObjects) all of which run just fine on Mac OS X / Mac OS X Server (you have access to J2SE 1.3.1, 1.4.2 and 1.5). This gives you good portability of server back-end between platform so your "data center" can remain flexible in how it is deployed.


For a thick-client on Mac OS X I would use Cocoa and Objective-C, it really is the fastest way to get a good solid and capable UI going on the Mac OS X. I personally prefer to go native on each platform for thick-clients since that often gets you a better platform citizen (with less work) then any xplat framework that you attempt to leverage. If you design your thick client core logic correctly your can make it very portable (usually use C or C++ for this myself) and wrap it with a layer of platform specific UI code (again usually Cocoa/Objective-C based on Mac OS X).

-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Developer Moving to Mac & Looking for Advice (From: Ima Newbie <email@hidden>)

  • Prev by Date: Attaching to a plugin
  • Next by Date: XCode 2.2 has broken my app's classloading
  • Previous by thread: Re: Developer Moving to Mac & Looking for Advice
  • Next by thread: Attaching to a plugin
  • Index(es):
    • Date
    • Thread