Okay, it's not that bad. But my experience with the two finds that SAX provides more control than DOM. Even though DOM Level 2 now provides a event system, SAX still provides the granularity that I need without the overhead and clunky interfaces. Even though my experience with event based programming may give me some bias towards SAX's ease of use, I still use DOM regularly. SAX may be harder for some to get their brains around because you have control over how you want the data model to look whereas DOM makes that decision for you. DOM could be considered the AOL of XML API's (Kidding!). For most developers purposes, they don't care what the data model looks like, they just wan't access to the it and thus the benefits of SAX may seem foreign.
Just to clarify the last sentence of my post, "Most developers don't care about the data model". That was meant in the general sense, not mean that developers don't care at all.