Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Jolly Roger <jollyroger@pobox.com>
Newsgroups: comp.sys.mac.system
Subject: Re: El Capitan worth upgrading?
Date: 18 Oct 2015 22:22:59 GMT
Organization: People for the Ethical Treatment of Pirates
Lines: 40
Message-ID: <d8ike3F6a5kU3@mid.individual.net>
References: <mvoohv$dgl$1@dont-email.me> <1mcdsor.1uh96nfzv769gN%dempson@actrix.gen.nz> <mvr6c7$amv$2@dont-email.me> <161020151222202118%nospam@nospam.invalid> <D24688D5.60695%usenet@gallopinginsanity.com> <mvslpa$48a$2@dont-email.me> <z6CdneDbCNR43r_LnZ2dnUU7-YXOydjZ@giganews.com> <D247D8A7.607E7%usenet@gallopinginsanity.com> <EaudnWwH_Z1VWr_LnZ2dnUU7-VmdnZ2d@giganews.com> <5622f919$0$29105$c3e8da3$38634283@news.astraweb.com> <gJOdnfFDWceIEr7LnZ2dnUU7-aGdnZ2d@giganews.com> <5623e4d5$0$32040$c3e8da3$a9097924@news.astraweb.com> <slrnn27q2b.1d43.g.kreme@amelia.local> <d8i84iF57f9U1@mid.individual.net> <562409f8$0$4209$c3e8da3$12bcf670@news.astraweb.com>
X-Trace: individual.net Q+xWFKJVg5vojQgxhiq0dgfbJNo7CRWlA/jTGjUFp7XeyPpxWb
Cancel-Lock: sha1:xAvkKPCgN54bKiclOEdrDZkttrk=
X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1<n@LQ!aZ7vLO_nWbK~@T'XIS0,oAJcU.qLM dk/j8Udo?O"o9B9Jyx+ez2:B<nx(k3EdHnTvB]'eoVaR495,Rv~/vPa[e^JI+^h5Zk*i`Q;ezqDW< ZFs6kmAJWZjOH\8[$$7jm,Ogw3C_%QM'|H6nygNGhhl+@}n30Nz(^vWo@h>Y%b|b-Y~()~\t,LZ3e up1/bO{=-)
User-Agent: slrn/1.0.1 (Darwin)
Xref: csiph.com comp.sys.mac.system:83750

On 2015-10-18, JF Mezei <jfmezei.spamnot@vaxination.ca> wrote:
> On 2015-10-18 14:53, Jolly Roger wrote:
>
>>>>> I'd assume that on older h/w Metal is not called at all.
>>>
>>>> Which means the application needs to have two code branches
>>>
>>> No, it doesn't mean that at all.
>> 
>> Of course, the best way to implement such a mechanism would be to do it
>> in the Cocoa APIs used by applicationsi in a way that is transparent to
>> developers...
>
> Which is exactly what I am saying. Apps make one Metal call. OS decides
> if the call cab be passed directly to Metal-compatible hardware or need
> to go though conversion to older API.

No, you are saying "the application needs to have two code branches",
which is actually the polar opposite of that.

> Forcing apps to duplicate their graphical code (one for Metal capable
> hardware, one for non-Metal) is bad when this could be done centrally in
> the OS APIs.

Who is forcing app developers to duplicate their graphical code?

> Unless, a decision was made that coding on Metal requires Metal capable
> hardware and the app will not launch on onder hardware.

You don't know?

> I have no idea which Apple chose.

Yet you seem very certain above.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR