As much as I hate to admit it, Tiger is dying and it's just not usable for real purposes today. Software support is just too bad.
I understand where you are coming from. When it comes to web browsing, if a PowerPC Mac is too slow to run TFF, then Tiger has no other reliable options.
It would be great to see continued development of TenFourKit, but it’s unlikely to happen. As we’ve discovered, even the Leopard WebKit folks are losing ground. The latest 603.x release had a download counter on SF within the 3000 range. This is a worldwide download count for a quality, free to use product... ouch.
It’s not that Tiger is dying, most would have considered it dead once Lion 10.7 hit. The only reason why we're feeling this pinch with Tiger is because of the limited browsing options for using websites like Youtube and Facebook. Tiger as an OS is the same as it was almost 10 years ago (10.4.11 was released November 14, 2007), so it all comes down to the web developers and their limited scope.
Most modern web developers (and app developers for that matter) don’t seem to care if their product is bloated or slow on old hardware. As far as they seem to be concerned, optimization is a thing of the past. Just look at the shift in mentality of something as deep rooted as the use of image compression. Most web devs don’t seem to mind pushing out multiple megabytes of images per page load nowadays. I recall when I was actively building websites for a living (2005-2011) there was an etiquette about keeping page load sizes down under 400k (total, including images). Now you're lucky if a basic page load is less than 3MB. Even the MacRumors home page pulled down a total of 6.48MB once I scrolled to the bottom and all of the on-demand images loaded.
Google on the other hand have had some bloating on their landing page, but still keep it under a megabyte at 987KB. Which is still pretty heavy considering it's just a search box!
Do you think there's a way to turn off Core Image? I hope so. It's a resource hog which my 12" G4 doesn't like, especially with its skimpy soldered GPU. Some people would probably agree with me.
It's not really something you can turn off, it's more of a technology made available to the system and apps. I highlighted in a separate thread that the PB12" does ALL of it's Core Image rendering on the CPU by design and only uses the GPU for Quartz Extreme (Hardware accelerated window compositing). Individual apps can choose to target the GPU on this model, but it must be done from the developer's position and isn't made available as an option to the end-user...
I believe it would hinder window management performance, but you could try turning off Quartz Extreme using the QuartzDebug developer tool. Many developers used a check for QE, which confirmed OpenGL acceleration to determine if CoreImage was accelerated and could then choose to deliver CI-enabled content or not. This might result in some apps appearing to run quicker, but with fewer visual features.
Just checked Wikipedia, Sawtooths actually do have a 350 MHz version.
I just thought that since Yikes! was the first version of the PMG4, and 350 MHz is such a low speed for a G4, it might have been the Yikes!.
Rational thinking hiccup.
Yes, I made the same assumption when I saw the MHz rating, then I noticed it had an AGP slot. I wrote a whole thread on this...
I enjoy seeing low-spec hardware operating efficiently. To be honest, the 350Mhz G4 running Tiger with enough RAM, a capable GPU and a fast enough boot volume actually feels like a decent machine. For productivity purposes, you'd hardly notice it was under 1Ghz. It's just when you try loading up a web browser that you are reminded of the specs.


