cvs commit: src/sys/compat/linux linux_socket.c

[juli mallett]

* Paul Richards <paul at originative.co.uk> [ Date: 2005-03-10 ]
	[ w.r.t. Re: cvs commit: src/sys/compat/linux linux_socket.c ]
> On Thu, Mar 10, 2005 at 06:06:16PM +0100, Dag-Erling Sm?rgrav wrote:
> > Paul Richards <paul at originative.co.uk> writes:
> > > Imagine something like Photoshop being written on the most recent
> > > version of Mac OS X and finding that compatibility only worked
> > > forward.  That would mean that most users out there would have to
> > > upgrade their OS in order to use the most recent version of Photoshop!
> > 
> > Yes, that is usually how it goes.
> 
> I don't believe it does. Can anyone provide real world examples of
> this happening that we can consider?

A number of Mac OS X applications target 10.2 and up, now.  Some apps
(macam.sf.net comes to mind) released stuff before then which is broken
on newer Mac OS X, but can be fixed for 10.2.  The 10.2 fixed stuff
will not work on 10.1 or earlier.  Apple provides "cross development"
tools to build for just about every version of Mac OS X.  But most sane
people?  They target 10.2+.  Even though I'm sure on a mailing list
somewhere, someone inside Apple who never seems able to find anything
better to do is whining on some mailing list that doesn't care about
how they're breaking all sorts of ABI, API, and Scary Monkey compat.
Their cries of DOOOOOOOOOOOM go unheeded.  So will yours.