Do people still use XML?
-
codewitch honey crisis wrote:
But I don't want to bother if everyone hates XML.
Aw, ffs, most people will not even know that it is being used. We're not religious, so we can't burn XML just because a few people don't know what it is for. If you create entire databases in XML, you'll hate it, yes. If you use it as a communication-protocol, you'll hate it too. Use it as an exchange-format, and it will work perfectly. I would store a tree in an in-memory SQLite3 database. Quick, efficient, and easy to write to a SQLite-db on disk and have the user send you their tree by mail, if you need it for debugging.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I'm not even using the XML. It's just a feature i'm thinking of adding for end user devs that use my stuff.
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'm not even using the XML. It's just a feature i'm thinking of adding for end user devs that use my stuff.
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.
Consider yourself to be SQL Server; do you allow export in XML, or would you prefer not to because a few people "hate it"? Programming isn't politics, technologies don't have to be popular.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
Consider yourself to be SQL Server; do you allow export in XML, or would you prefer not to because a few people "hate it"? Programming isn't politics, technologies don't have to be popular.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
I do crap that's not popular all the freakin time. :)
".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, 2013 -
I do crap that's not popular all the freakin time. :)
".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, 2013#realJSOP wrote:
I do crap that's not popular all the freakin time. :)
Like asking who took your template-permissions? :laugh:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
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.
codewitch honey crisis wrote:
Do people still use XML?
Yes, at least I do (and the previous department where I was working too) If it is worth your time to add and mantain... only you can answer the question
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
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.
Right tool for the right job, doesn't matter if others use it or not!
I do all my own stunts, but never intentionally! JaxCoder.com
-
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.
If you need to guarantee that your objects stay in order, use XML. JSON is subject to the engine that's parsing it, where XML is - well - XML. The only thing I think most real programmers hate is any form of visual basic.
".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, 2013 -
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.
I use XML for lots of things but mostly where I need a desktop app to communicate with a web resource either to receive/send bulk data (usually via sql to xml) or little things like FTP credentials (encrypted of course) or program/file updates. I've always found XML to be extremely easy to use. :)
"Go forth into the source" - Neal Morse
-
Consider yourself to be SQL Server; do you allow export in XML, or would you prefer not to because a few people "hate it"? Programming isn't politics, technologies don't have to be popular.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
in sql server the XML might actually be useful. from a parse tree, less so
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.
-
Right tool for the right job, doesn't matter if others use it or not!
I do all my own stunts, but never intentionally! JaxCoder.com
i personally don't need the feature. i'm designing an API. the feature is for others, so the question is, do you use XML to do the job these days?
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.
It's probably one of those cases where, unless you need to use XML, use JSON. From your problem statement it seems that you need to use XML, so use it. Tough if everyone hates it.
Kevin
-
It's probably one of those cases where, unless you need to use XML, use JSON. From your problem statement it seems that you need to use XML, so use it. Tough if everyone hates it.
Kevin
Unfortunately, i can't readily use JSON because node order is significant, and JSON allows for reording of child nodes.
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.
-
in sql server the XML might actually be useful. from a parse tree, less so
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.
codewitch honey crisis wrote:
in sql server the XML might actually be useful. from a parse tree, less so
That I don't know, but it doesn't change the point that you asked whether XML is still appropriate. I think it may be moreso than a CSV file ;)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
codewitch honey crisis wrote:
in sql server the XML might actually be useful. from a parse tree, less so
That I don't know, but it doesn't change the point that you asked whether XML is still appropriate. I think it may be moreso than a CSV file ;)
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
One time I built a mapper that allowed you to represent hierarchical data in tabular format, using the same technique used by MS SQLXML, including the column naming style and such. It was primarily used for accessing RDBMS systems using XML and XPath but you could use it on anything that can be tabular including CSV files and even HTML forms
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.
XML is widely used. And, it's often a lot more convenient than JSON, since you can create a DTD that lets the parser do a lot of the grunt work for you. I use it all over the place. I only use JSON if it's already part of the protocol of a device I'm talking to or it's stuff related to talking to Javascript in a browser.
Explorans limites defectum
-
One time I built a mapper that allowed you to represent hierarchical data in tabular format, using the same technique used by MS SQLXML, including the column naming style and such. It was primarily used for accessing RDBMS systems using XML and XPath but you could use it on anything that can be tabular including CSV files and even HTML forms
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.
You'd think that after 27 years we would have agreed on a standard way to access the database. From SQL92 and ODBC to ADO and DAO to .NET providers and connections, we have this long list on standard ways, and you introduce yet another way that is built on existing standards. :laugh:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
-
You'd think that after 27 years we would have agreed on a standard way to access the database. From SQL92 and ODBC to ADO and DAO to .NET providers and connections, we have this long list on standard ways, and you introduce yet another way that is built on existing standards. :laugh:
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^] "If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
That's why standards are great - we have so many to choose from! :^)
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.
-
XML is widely used. And, it's often a lot more convenient than JSON, since you can create a DTD that lets the parser do a lot of the grunt work for you. I use it all over the place. I only use JSON if it's already part of the protocol of a device I'm talking to or it's stuff related to talking to Javascript in a browser.
Explorans limites defectum
I mostly use JSON these days for data interchange, but I hear you about typing. That being said, there's a spec for JSON schemas, and many engines already support validation using them. I don't use them myself. In the real world, most JSON is machine generated, which means it doesn't necessarily need heavy validation unless its coming from somewhere external (to avoid possible exploits)
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 mostly use JSON these days for data interchange, but I hear you about typing. That being said, there's a spec for JSON schemas, and many engines already support validation using them. I don't use them myself. In the real world, most JSON is machine generated, which means it doesn't necessarily need heavy validation unless its coming from somewhere external (to avoid possible exploits)
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.
For me lots of it is user configuration, or data from external devices or servers, none of which can be assumed to be even reasonably correct. And, ultimately, it all really probably should get good validation. If your program croaks because of an error in another program, that's not a good thing.
Explorans limites defectum
-
For me lots of it is user configuration, or data from external devices or servers, none of which can be assumed to be even reasonably correct. And, ultimately, it all really probably should get good validation. If your program croaks because of an error in another program, that's not a good thing.
Explorans limites defectum
that's what error handling is for. Validation just lets you throw sooner. A lot of times that's not even necessary.
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.
