• 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: optimizing compilers
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: optimizing compilers


  • Subject: Re: optimizing compilers
  • From: Nat! <email@hidden>
  • Date: Sat, 2 Feb 2002 20:18:03 +0100

On Samstag, Februar 2, 2002, at 07:55 Uhr, email@hidden wrote:

I think that the combination of Quartz and broken Cocoa display semantics is
slow because my company sells a high end vector animation application that
is much faster on a 266Mhz Pentium PC running Openstep than it is on a
450Mhz G4 running OS-X. I have posted many times on this subject. Part of
the problem is that the Foundation classes got much slower between Rhapsody
DR2 and OS-X. Part of the problem is that Quartz vector rendering is slower
than Display Postscript used to be. We can work around the Foundation
framework problems, but we are stuck with slow (but admittedly more capable)
Quartz.

I imagine you have benchmarks that support these assertions; but more to the point, your application is a very special case. I stand by my assertion that for the typical user who perceives slowness in most operations on OS X, Quartz is not a factor.

On what do you base your assertion ? And if Quartz is no factor, what are the relevant factors ?

Nat!
------------------------------------------------------
Some people drink deep from the fountains of life, and
some just gargle. -- DLR


References: 
 >Re: optimizing compilers (From: email@hidden)

  • Prev by Date: Beginner Question
  • Next by Date: Re: How to use functions of Kernel.framework? (especially Blowfish)
  • Previous by thread: Re: optimizing compilers
  • Next by thread: Re: optimizing compilers
  • Index(es):
    • Date
    • Thread