• 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: Why use frameworks?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why use frameworks?


  • Subject: Re: Why use frameworks?
  • From: Jack Repenning <email@hidden>
  • Date: Fri, 20 Jul 2007 10:39:35 -0700

On Jul 20, 2007, at 9:56 AM, Chris Ridd wrote:

Wil Shipley wrote something about frameworks a while back:

<http://wilshipley.com/blog/2005/11/frameworks-are-teh-suck-err.html>


Yeah, what he said ;-)

1. Frameworks make a lot of sense if you expect many, many programmers to use them in their own development. Not only do they provide shared code, but also they can provide separate compilation (save build time), and handy ways to organize an extensive library of documentation. "Many, many" is a fairly vague number, but it's definitely greater than one. Cocoa qualifies. Doesn't sound like your stuff does.

2. Frameworks make a lot of sense if you expect many, many programs on a single system to use them. The shared code saves space both on disk and in memory, the single copy simplifies updates. "Many, many" is still vague, but it's definitely greater than two. Core Audio qualifies. Doesn't sound like your stuff does.

3. Frameworks make a lot of sense if they're provided by the operating system itself, so that programmers (#1) can confidently expect them already to be in place for their programs (#2), so they are freed from having to distribute them, manage versions, and so forth. Again: as your email address is not "@apple.com," you don't seem to be buying much here.

There is one thing that you might be careful about: if you're simplistic about how you eliminate this framework, you could end up with two copies of each source file, which would be chaos. Whatever their other limitations, Frameworks do provide a means to tell Xcode to share one copy of the code among several targets or projects. But there are other ways to achieve that; this benefit alone may not be worth the costs you're paying. Simplest case, just include all your source in one project, with separate targets for each of your two programs (each of which includes the sources for what you now organize into a framework).

-==-
Jack Repenning
Chief Technology Officer
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
office: +1 650.228.2562
mobile: +1 408.835.8090
raindance: +1 877.326.2337, x844.7461
aim: jackrepenning
skype: jrepenning




_______________________________________________ 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
  • Follow-Ups:
    • Re: Why use frameworks?
      • From: Mike Blaguszewski <email@hidden>
    • Re: Why use frameworks?
      • From: Randall Meadows <email@hidden>
References: 
 >Re: Why use frameworks? (From: Chris Ridd <email@hidden>)

  • Prev by Date: Re: replacement for CW compare?
  • Next by Date: Re: Xcode and Javadoc
  • Previous by thread: Re: Why use frameworks?
  • Next by thread: Re: Why use frameworks?
  • Index(es):
    • Date
    • Thread