Re: Fixing what's broke
Original Message From: "Max Toro" > On Sat, Dec 11, 2010 at 11:48 AM, Pete Cordell wrote: >> Original Message From: "Max Toro" >>> >>>> I've put in a number of posts what I think the benefits of the change >>>> are. I >>>> also think that in a mobile and wireless world, especially where we >>>> have >>>> small intelligent devices like body area networks, zigbee and, in the >>>> future, corn flake packets telling us when they're empty that we can't >>>> just >>>> assume that memory is free, and bandwidth unlimited. >>>> >>>> What do you see as the benefits of always insisting that everyone does >>>> >>>> <trajectory:initialVelocityVarianceCoefficient>1</trajectory:initialVelocityVarianceCoefficient>? >>> >>> application/x-www-form-urlencoded and JSON are more condensed >>> representations, if that's what you are looking for. >>> If you change XML to fit every possible use case it's going to make it >>> worse. >> >> Worse in what way? > > More complex to understand. I'm afraid I don't buy that. It's always worth being aware of incremental complexity, but this is nothing compared to what you have to understand to write code these days. If it saved you having to understand application/x-www-form-urlencoded and JSON as well then it's actually easier to understand. Pete Cordell Codalogic Ltd Interface XML to C++ the easy way using C++ XML data binding to convert XSD schemas to C++ classes. Visit http://codalogic.com/lmx/ or http://www.xml2cpp.com for more info
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format