This is kind of funny to me, and makes you think a little bit. I do think 10.4 is one of the most stable now. It was a rough ride though. I actually had my iBook G3 back when Tiger was still the latest OS, and I had some issues. I had less issues than Windows XP, but it definitely had some. My father's iBook G4 was on 10.3.9, and he never had issues.
Tiger got up to 10.4.11, which is an interestingly high version. In my head this meant it needed a lot of fixes and optimizations. I remember when 10.4.10 came out and thought "huh, wasn't expecting that". Then 10.4.11 came out, after Leopard's release if I'm not mistaken, which also caught me off guard. I was also like 15 or something at the time so take that as you will lmao.
Since 10.4.11 I can't recall having any major issues, even today.
The only thing Tiger does now that pisses me off is when you highlight icons, specifically a group of icons, it'll like.. Only partially highlight some of the icons. It doesn't affect functionality, but its weird, and it does bother me when it happens.
I've run this down before, but it bears repeating I guess…
Anyway, the vast majority of my Tiger use was at work. Everything we needed was on server shares, kept on the PC server (Windows 2003 SBS at the time) and shared to the network via SMB. AFP was not an option, as the only way I could use that was to install FSM (File Services for Macintosh). That presented an OS7/8 era version of AFP that required 8 letter filenames with three letter extensions. In the meantime, it eliminated SMB sharing for any Mac shares entirely.
So, to even connect, I had to have security reduced on the server. Passwords sent in clear text, SMB signing off. Once I worked that out, then I had to be prepared to accept that I could only make two Finder commands at a time and they both had to be similar. For instance, two copy operations to or from the server shares. Or two file deletions. I could not initiate a file copy AND a deletion, or make three Finder commands without getting SBBOD. And once I got SBBOD, that was it. There was no recovery, no waiting for Finder to stop spinning. It was a forced restart every time.
Files didn't want to save over the network from inside programs, and I had issues with overwriting files. It got to such a frustration level that I ultimately ended up installing DAVE on both production Macs running Tiger.
Last but not least, Tiger has an archaic printserver. I didn't find that out until around 2013 when I attempted to share the postscript printers from a G4 running Tiger so that the new MacPro could print correctly. Tiger's printserver would shut down repeatedly after printing a job and the only recourse was a reboot. Bit of a problem when you're running that G4 headless and controlling it through screen sharing.
We eventually installed Leopard on the production Macs and the majority of my network issues went away.
Tiger was pretty stable on my home Macs, which is why I didn't have much issue with installing Tiger Server on my G3 B&W. But, I was never trying to do much at home of what I did at work. And I had mostly Macs, no PC server.
My experience is largely not what everyone else's was/is with Tiger. It's unfortunate, but is what it was.