VivienM wrote on 2024-02-15, 23:11:Tiger and Snow Leopard make sense as retro OS X versions in a way that, say, Leopard doesn't.
Tiger has classic (although do yo […]
Show full quote
Jo22 wrote on 2024-02-15, 03:58:
PS: There are of course als Tiger (10.4) fans out there.
Essentially, Tiger is to PPC users what Snow Leopard is to x86 Mac users.
They may still have an interest in 64-Bit G5 systems or running Classic Environment.
Tiger and Snow Leopard make sense as retro OS X versions in a way that, say, Leopard doesn't.
Tiger has classic (although do you really need classic on a retro system that can boot OS 9?), much faster performance, and a certain degree of maturity.
Snow Leopard is the last version with Rosetta and therefore the last Intel version able to look back on the PPC era.
Plus I thiiiink every Intel machine can run Snow Leopard, including the early 32-bit ones.
But what's the argument for Leopard? Sure, it's the last PPC OS, but it's relatively slow on G4 hardware.
The one notable benefit, but I'm not sure how much it matters for a retro system,
is that there's much better software compatibility. e.g. to pick a bad example, VLC - Tiger gets 0.9.10, Leopard gets 2.0.10, Snow Leopard gets 2.2.8,
and somehow the current version of VLC is still supported on Lion and newer.
But again... what are you doing with VLC on a retro G4 that can't be done elsewhere or using 0.9.10?
And I think a lot of people supported Leopard for a long time because they didn't want to completely leave PPC behind... but really, who wants to run ~2011-2012 software on a PPC...
I mostly agree with you, I think.
I suppose Leopard was essentially both the first and last power user OS for the Power Mac G5.
The only Apple OS that took full advantage of the G5 processor.
But at same time, Leopard had lacked Classic Environment, which like Rosetta was very important to the Mac diehards.
Classic (on Tiger) had allowed them to keep running them all their legacy stuff
(CodeWarrior, old productivity software etc), side by side with modern applications.
Almost 20 years worth of software, way down to 1984.
So yeah, it's a bit hard to understand which kind of user Leopard tried to serve.🤷♂️
If Leopard had Classic Environment, it would have been a true hit. 😃
Because, all the new graphics effects and new APIs were nice to have.
The 64-Bit Mac application support, too. - Tiger did merely support 64-Bit applications of unix type.
On the other hand, Tiger was really cheerful and easy to use. It was very lightweight, too.
But not a full unix system like Leopard was, I suppose.
All in all, it's a bit like the force vs the dark side of the force (star wars).
PS: I think there was a beta of Snow Leopard for G5 architecture. Some sort of developer preview..
Unfortunately, G5 support was being dropped before Snow Leopard got released.
Edit: About Classic vs real OS 9.:
I'm with you about being able running OS 9 natively, if possible.
Using it as an independent OS rather than some runtime is doing it justice.
For anything multimedia/gaming, native Mac OS 9 is a must (3D, audio processing, MIDI etc).
There, you have Voodoo 2, OpenGL, QuickDraw, QuickDraw 3D and QuickDraw 3D RAVE! 😁
On the other hand.. Classic Environment is nice to have as an optional compatibility layer for those two or three beloved applications.
As a gimmick, so to say. On an otherwise pure OS X Macintosh, with OS X software.
- Like "XP-Mode" was being used on Windows 7 back in the day. It was also very limited compared to real XP (2D, software rendering).
Personally, I once saw a dire need for Classic myself.
On my shortwave hobby computer, there's a WinRadio receiver with an USB/Serial interface.
https://winradio.com/home/macradio-g2.htm
The control software was being written in the 90s, for Windows 95 (Win32) and Mac OS 8/9 (native API).
There's no Cocoa version (OS X) or Carbon version (Mac OS/OS X).
Without Classic or Virtual PC (running Windows) or an Mac OS 8/9 emulator (in early development back then),
there wouldn't have been a way to use that device on a more modern Macintosh anymore.
Except by booting OS 9 directly, but that would mean that the ham radio software for OS X wouldn't be available same time.
Which would be sad, because the receiver's audio is being processed by these OS X applications (Cocoa Modem or Multimode; decoding RTTY, SSTV etc).
These are moments in which I wonder why Mac developers didn't use the Carbon library more often. 🙁
Especially towards the end of the 90s, when OS X was on horizon..
(Carbon is a subset of the old Mac API and Carbon applications can be run on Mac OS 8/9,
OS X on Power PC (any version, incl. Cheetah!) and on Leopard/Snow Leopard on Intel.)
That being said, these aren't exactly gaming related things.
It just came to mind.
In some cases, Classic won't do, also.
For example, if applications from the 80s want to talk to one of the internal serial ports.
In such a case, merely a native Mac OS with a real serial port will do.
The internal modem port can be routed to an external connector, for example.
See GeeThree Stealth Serial Port, Jamport G4 etc.
Edit: Edited. Formatting fixed (on PC).
"Time, it seems, doesn't flow. For some it's fast, for some it's slow.
In what to one race is no time at all, another race can rise and fall..." - The Minstrel
//My video channel//