>People still use OS9! It's me, I'm people. I just like programming, I like this style of game, and I like giving myself a reason to turn on my iBook or iMac.
If you don't happen to have your 2000s-era iMac or iBook running OS 9 currently in arm's reach here's an online version of the same sort of game: https://www.unixpapa.com/floodit/?sz=14&nc=6
> The approach I use is to play for penetration. I aim for the opposite corner. Rarely the obstacles have too much repetition. I would allow for this by requiring a wedge shape having a favorable ratio of base size to length.
qemu actually tries to emulate all of the hardware in a Mac; also, I believe its CPU emulation is just interpreted though someone correct me if I'm wrong. SheepShaver emulates the CPU with a JIT and then patches the emulated MacOS so that calls to it run as native code.
SheepShaver is hacky, I know it since BasiliskII times, same people.
SS is faster, but nowadays the gap against Qemu is not that big on a modern machine.
Also, Qemu will provide an ATI Rage device for the G3/G4 machine, so you may be able to correctly play a good chunk of 3D games released for Mac OS 9.
Writing a Mac application in GTK is, again, not conducive to the goal of learning to program a new platform. Wrappers such as GTK around native objC, Cocoa, and Swift are a distraction from the main purpose of learning those things.
No, I didn't mean to GTK, but for Carbon or whatever API Mac OS used.
The game is already on GTK and JS, so it would be easily portable
as they are really simple games (they have even an Android port).
It's not that easy. Carbon is largely a subset of the classic MacOS toolkit APIs reimplemented in MacOS X to provide a migration path for existing application to MacOS X. IIRC carbonized applications commonly targeted version going back to MacOS 8.6 - 10.x with a single executable. From my unreliable childhood memories the next common range started at MacOS 9.0 (or 9.1).
Rosetta was a PowerPC CPU emulator that allowed running any kind of PowerPC OS X application on Intel Macs.
Carbon was a set of largely OS 9 compatible APIs that allowed an easy transition for apps that could be recompiled.
Classic was a virtualized OS 9 environment available on OS X (up to 10.4 Tiger, PPC Mac only) that allowed running unmodified binaries for pre-OS X Macs. Most things that didn't require special hardware access or precise timing ran fine, but things like real-time audio and MIDI applications did not.
I miss the spatial properties of classic MacOS. Windows would always be in the same spot when you window shaded them, files would be in the same spot in a folder unless you cleaned it up.
>People still use OS9! It's me, I'm people. I just like programming, I like this style of game, and I like giving myself a reason to turn on my iBook or iMac.
So good