Do people still use XML?
-
I would not use XML if there was serious volume involved, I've seen systems fail using xlm when attempting to transfer gb between systems. As others have said use the correct tool for the job no matter whet the "popularity" you perceive is.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
The "job" is undefined. I'm making an API. Anyway, I'm not sure I'm going through with this bit. Besides I have other stuff to work on that has taken precedence.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
There’s a way around the big-ass file problem, but it comes with restrictions. A few months ago, I wrote some code to load files that were as large as 8gb. It could probably go larger, but that’s the largest file I had.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013I design pretty much everything assuming my files are going to be 16GB meaning i use streams and (when necessary) pull parsers. I *always* chunk, absent the narrow case where it doesn't make sense to.
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
There’s a way around the big-ass file problem, but it comes with restrictions. A few months ago, I wrote some code to load files that were as large as 8gb. It could probably go larger, but that’s the largest file I had.
".45 ACP - because shooting twice is just silly" - JSOP, 2010
-----
You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010
-----
When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013It was a few years ago and was basically transferring a daily snapshot of a banking system to a reporting/analysis tool with biztalk in the mix. System was totally unwieldy and got canned before it was completed. XML was never used again as a transfer medium.
Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP
-
I can't use JSON for rendering a parse tree because JSON does not preserve the order of subelements and because of the way multiple values are presented it gives json problems. XML can do it, because XML preserves element order and an element can be present more than once within its parent container. But I don't want to bother if everyone hates XML. What would you do?
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
Prolly stating the obvious, but can you package subelements as items in an array? /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
they need names. i could, but the resulting json isn't worth it [ {a: b}, {c: d} , {e: f} ] sucks, you know? better to just use xml
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
-
I can't use JSON for rendering a parse tree because JSON does not preserve the order of subelements and because of the way multiple values are presented it gives json problems. XML can do it, because XML preserves element order and an element can be present more than once within its parent container. But I don't want to bother if everyone hates XML. What would you do?
When I was growin' up, I was the smartest kid I knew. Maybe that was just because I didn't know that many kids. All I know is now I feel the opposite.
Use PostScript. It's like a version of XML that hasn't had its bollocks lopped off.
I wanna be a eunuchs developer! Pass me a bread knife!
