Linked by Thom Holwerda on Fri 13th Jul 2012 23:39 UTC
Thread beginning with comment 526881
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Too many platforms
by malxau on Sun 15th Jul 2012 22:28
in reply to "RE[4]: Too many platforms"
I tried Netscape 4 on a Linux 2.6.32, works without problems. Just have to install some older libraries through my package manager.
Interesting. I have incompatibilities in libstdc++, where the ABI has changed so I can't simultaneously support NS4 and anything else...
"What Mac OS X from the early days are now deprecated?
...
Don't just reflect the things I said about Win32 on Cocoa, this is stupid. "
I didn't, this point was purely OS X from the outset. Note the original poster was talking OS X, not Cocoa.
Why on earth do you reference "Carbon" here?
Well, it's still OS X, which is what the original poster was referring to.
But you see the same with Cocoa too, just with simple googling...
https://developer.apple.com/library/mac/#documentation/Cocoa/Referen...
RE[5]: Too many platforms
by ulricr on Mon 16th Jul 2012 13:48
in reply to "RE[4]: Too many platforms"
Why on earth do you reference "Carbon" here? Carbon was also deprecated when MacOS X was introduced in 2001. Developers were NEVER supposed to write Carbon applications when targeting MacOS X. Cocoa is and has always been the native API of MacOS X and it is STABLE.
not true. I was there at the OS X launch and Carbon and Cocoa were presented at equals. Java was as well.. Stuff changes. Cocoa was also the only way to access the full quicktime API (quicktime is not just a file format, it's a full multimedia API). Apple's own apps, like Final Cut Pro, were all written in Carbon. It's only at the switch for 64-bit that Apple decided to drop carbon, and that surprised everyone -- even some internal groups.
It makes no sense to talk about 30 years of Windows API, but only start in 2001 for Apple, btw.
Btw from year's WWDC, objective C garbage collection will be deprecated now.




Member since:
2009-09-23
It doesn't. "
Try this experiment. Get a cross-platform piece of code from the late 90s - say, Netscape 4 - and try to run it on Windows, Linux, and Mac OS. It will run on one of them, guess which... [/q]
I tried Netscape 4 on a Linux 2.6.32, works without problems. Just have to install some older libraries through my package manager.
As I already said, the 18-year-old image viewer "xv" still runs fine on current Linux distributions. One of my friends is still using it.
xxxxxxxx@yyyy:~> which xv
/usr/bin/xv
xxxxxxxx@yyyy:~> uname -a
Linux zlogin 3.2.0-0.bpo.1-amd64 #1 SMP Wed Jan 25 00:15:47 UTC 2012 x86_64 GNU/Linux
xxxxxxxx@yyyy:~> xv
I just ran it.
It's not about the power - it's about having four incompatible versions of Qt in the last 15 years. "
Doesn't matter at all. If you have applications compiled against Qt3, you just download and install Qt3 libraries and you're done.
You have the same problems on Windows in this regard. If an application was compiled against MFC4.2, you have to have MFC42.DLL on your system, otherwise it won't work.
None. MacOS X still has the same native API it got when it was introduced, namely Cocoa which is based on NeXTStep which has been around since the 80ies. "
It has the same design, but many APIs have been deprecated - or just plain broken - in the meantime. [/q]
Don't just reflect the things I said about Win32 on Cocoa, this is stupid.
https://developer.apple.com/library/mac/#documentation/Carbon/Refere...
Why on earth do you reference "Carbon" here? Carbon was also deprecated when MacOS X was introduced in 2001. Developers were NEVER supposed to write Carbon applications when targeting MacOS X. Cocoa is and has always been the native API of MacOS X and it is STABLE.
The only API which is constantly broken is Win32 and other stuff from Microsoft. Ask any wine developer or developers at Steam.
For example: http://www.rockpapershotgun.com/2011/08/03/why-steam-makes-you-inst...
Adrian