this is your idea of stability? an error message with no information to troubleshoot on?
There's plenty of info following a kernel panic, including a full dump you can run through GDB to see where exactly the panic occurred. You just need to know where to look for it.
When the OS is panicing, it starts dumping as much information as it can. A screen or console is the wrong place to do it, because the user can't have easy access to it.
If you had done any Unix work, you'd know this is how it goes. You want to bring the system back up first, then you want to troubleshoot. Logs/dumps are the best place for information.
The fact that you would use this against Macs shows how much you've yet to learn about Unix.