Generally, SAX is only there because you have massive documents to process, or very constrained resources. Of course, you're right to say SAX has a place, and I did really oversimplify things. If you're using Ruby or Django though, and not processing large documents, I doubt switching to SAX would be a low-hanging fruit.
Way too glib. There's lots of good reasons you may choose to go with that, and there's lots of reasons why you may not. DOM-based approaches pay a lot of resources for their functionality. If you don't use all of that functionality, you may lose over a SAX-based approach. If you're resource rich, hey, great, go with DOM unconditionally, but not all web apps are in that situation.
It's one advantage the XML ecosystem has over the JSON ecosystem; while JSON can be parsed in a streaming manner, you can generally count on a good XML event-based library for your environment, whereas streaming JSON parsing libraries seem more unusual. If you need it, you can count on it in XML.