Where to find Birdie?

[MskoDestny]

shit, yet fast operating system

I don't think that's terribly fair. Classic Mac OS generally had better usability (though having to manually adjust memory limits for software wasn't so nice....), but was a complete mess architecturally. It was a single tasking OS until System 5 came out in 1987 and multitasking was implemented as an extension until System 7. Even then it was a rather nasty hack that wasn't cleaned up until OS X. Further all file access went through the Finder and the finder could only support a single operation at a time until Mac OS 8.

Also keep in mind, that Commodore went under in 1994 roughly 3 years before the release of Mac OS 8. If you want to be fair you should be comparing Workbench 3.1 with System 7 (which to be fair to you, did have the Extension folder which is what you were specifically talking about).

Now Amiga OS had (and to an extent still has in Amiga OS 4) its own share of architectural warts, but for its time the design was quite clean.

price gouged market

Well only after Commodore went out of business. The machines were quite cheap for what you got when they were still in production.

[MskoDestny]

From using the upper 8-bits of address registers to hold data in old m68k releases,

This was a problem with applications (and extension) not the system itself. Even the Amiga wasn't immune to this sort of bad behavior (Amiga Basic anyone?)

to using exception traps for system calls,

This isn't completely unreasonable. On the 68000 the extra overhead doesn't buy you very much, but on later machines with MMUs such a mechanism is necessary to provide proper memory protection (not that classic Mac OS took advantage of that...).

The biggest problems were the hackish way multitasking was implemented and that file access was handled by an application (the Finder) rather than having proper layering.

They tried quite a while to make a next-gen Mac OS that would fix the problems, but they couldn't make it work so they gave up and bought NeXT instead.

I can't think of a single thing a cli does that a gui can't. And the gui method is much better for actual productivity, you don't have to keep listing crap out and memorising switches.

For one, command line programs are easier to script and I say this having used a number of automation tools for classic Mac OS. Certain bulk operations are much faster to do via a CLI as well. Deleting all the files that end with a certain string is trivial via a CLI with wildcards, but requires a fair amount of manual work in a GUI. This not to say that it's superior for everything, but it is handy to have around.