To view parent comment, click here.
To read all comments associated with this story, please click here.
Yeah you're right, XML parsers are HUGE!!!
http://expat.sourceforge.net/ (~300K source code)
I think he is talking about the ratio of code to resulting work that comes out the other end; that doesn't include the fact that when XML data starts to become big; it is overly verbose and bloated - hence a whole new industry based around XML compression/Binary-XML.
Couple that with the problems that SOAP have in regards to scalability, one wonders whether SOAP and XML are merely pathetic attempts by Microsoft to adopt technologies simply because they have no heritage to SUN or anything from the 'old world' - it seems to me they'd rather have a poorly scalable SOAP than using CORBA which has been rigourously tested for many years.
>>Note that XML is _not_ a proper text stream because it >>can't be parsed without an insanely huge and complex XML >>parser.
>Yeah you're right, XML parsers are HUGE!!!
>http://expat.sourceforge.net/ (~300K source code)
Ehh, are you trying to be sarcastic? 300K *is* huge.




Member since:
2005-07-07
And I thought Unix had solved this 30 years ago...
"Write programs to handle text streams, because that is a universal interface." -- Doug McIlroy
Yeah text is really ^M
universal, there are ^M
no cœmpatibility problems at all.
Note that XML is _not_ a proper text stream because it can't be parsed without an insanely huge and complex XML parser.
Yeah you're right, XML parsers are HUGE!!!
http://expat.sourceforge.net/ (~300K source code)
There are many languages that don't have XML parsers(and there are many devices that don't have enough resources to run a standard XML parser), there are very few languages and systems that can't do string/text manipulation.
Yeah, there's lots of programming languages that can't interface with C libraries.
Well, I'm off to write a program that dumps binary search trees off my company's mainframe to a text stream for access on my graphing calculator...toodles.