My family never used to be so keen on TV, then my mom started suffering from mental problems, and believed the TV was talking to her - so we threw the thing out.
The TV company did of course send us letters, kinda rude too, about pay up or else (Not even, if you have a tv pay up, just told us to pay..)
We just ignored them, then after I think a year, we got a letter saying that they were no longer legally allowed to check us, or send us letters for 3 years, without counting as harrassment..
So.. we got a TV for 3 years.. hehe Although even when free its not worth it
Not to mention supporting different language encodings.
Re:Why parse XML in the first place?
on
Perl & XML
·
· Score: 2, Insightful
The trouble is that people use it wrongly. (IMHO)
If it is done right, most of the time you should never have any actual XML text!
Store the data you are using in DOM, and manipulate it there. Store the data in DOM format on the disk, with a way to dump to XML if you have to (which you rarely will). Compile your Schemas, etc.
I'm also not sure why you imply it is costing time using XML - one of the ideas is that it is supposed to save time - and it does. I can write schemas to validate the output and input, write XSL's to transform the data to anything, and so on.
Slashdot Mirror
My family never used to be so keen on TV, then my
mom started suffering from mental problems,
and believed the TV was talking to her - so
we threw the thing out.
The TV company did of course send us letters,
kinda rude too, about pay up or else
(Not even, if you have a tv pay up, just told us
to pay..)
We just ignored them, then after I think a year, we got a letter saying that they were no longer legally allowed to check us, or send us letters for 3 years, without counting as harrassment..
So.. we got a TV for 3 years.. hehe
Although even when free its not worth it
Wow!
;)
The one other slashdotter that realises you don't have to actually store the data in XML form!
And I was beggining to feel lonely...
Not to mention supporting different language encodings.
The trouble is that people use it wrongly. (IMHO)
If it is done right, most of the time you should never have any actual XML text!
Store the data you are using in DOM, and manipulate it there. Store the data in DOM format on the disk, with a way to dump to XML if you have to (which you rarely will). Compile your Schemas, etc.
I'm also not sure why you imply it is costing time using XML - one of the ideas is that it is supposed to save time - and it does.
I can write schemas to validate the output and input, write XSL's to transform the data to anything, and so on.