From my perspective... I prefer SXML when I am processing XML that other's have made. I prefer Xexprs when I am making my own.
SXML has a nice XQuery implementation and the parser is much better (faster/streaming/etc) than the (require xml) parser. Jay 2011/2/19 John Clements <[email protected]>: > I think this is mostly a question for Neil... > > What are the advantages and disadvantages of SXML vs. xexprs? I've googled > for this, but none of the high-ranked hits attempt to actually catalog their > relative virtues. > > Here's what I can come up with: > > namespaces : xexprs don't handle namespaces, right? > > web-server support: Jay's recent changes make the web-server relatively > representation agnostic, but the built-in methods are there for xexprs and > not for SXML > > parsing : I get the sense that the SXML parser is way more general, but it's > not clear to me when this is useful. > > serialization : I think that SXML serialization produces better results... > > entity support: they support it in different ways, right? > > representation choices: the SXML choice (@ for attrs) seems less error-prone, > though the choice of '@' is really unfortunate when I want to abstract using > the 'at-exp' languages. > > > > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/users > -- Jay McCarthy <[email protected]> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93 _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/users
