blocks|key|1604957|text|存储图像。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1604958|尤其是作为表示单个字节的数字数组。|1604959|http://thedailywtf.com/Articles/Oh,-XML.aspx|offset|length|1604960|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|18|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@$F|R|G|S|1|T]]|A|$]]|$1|H|3|-4|5|6|7|U|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|E]]]]

Storing Images. 

Especially as an array of numbers representing individual bytes. 

<a href="http://thedailywtf.com/Articles/Oh,-XML.aspx" rel="noreferrer">http://thedailywtf.com/Articles/Oh,-XML.aspx</a>

blocks|key|1390121|text|人们在他们的简历上注明了"XML编程语言“的经验。即时的圆形文件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390122|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

People noting experience with the "XML Programming Language" on their CV. Instant round-file.

blocks|key|1605061|text|将其用作数据库，在每次更新/插入时重写该文件。一直都在看这个。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605062|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Using it as a database, rewriting the file on every update/insert.
See this all the time...

blocks|key|1605104|text|关于一个政府项目|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605105|包装在XML中的XML|1605106|原始XML中的数据已经有8层深了。|1605107|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

On a government project

XML wrapped in XML wrapped in XML wrapped in XML

The data in the original XML was already 8 layers deep.

blocks|key|1390296|text|当我看到人们使用SAX解析器，而他们真正需要的是DOM解析器时，它总是让我感到恼火。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390297|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It always bugs me when I see people using a SAX parser when what they really need is a DOM parser.

blocks|key|1605271|text|在欧洲，似乎有某种标准化的XML文件格式用于存储银行交易。我见过一场关于编写一种新的XML解析器的竞赛，该解析器能够比其他方法更快地解析那些文件(大于10+GiB+)。在这样的文件大小下，我不认为XML是一个很好的文件格式选择。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605272|还有另一个经常让我感兴趣的东西:某种Java对象序列化，它似乎只适用于三个不同的标签：java、object和void。剩下的工作都是通过两三个属性和大量的嵌套来完成的。|offset|length|style|CODE|1605273|entityMap^0|0|17|4|1C|6|1J|4|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]|$D|P|E|Q|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|I|$]]

There seems to be some sort of standardized XML file format used in Europe for storing bank transactions. I've seen a contest for writing a new XML parser that is able to parse those files (that are > 10 GiB in size) quicker than other approaches. At those file sizes I don't expect XML to be a very good choice of file format.

And another one that bites me regularly here: Some sort of Java object serialisation which seems to work with exactly three different tags: <code>java</code>, <code>object</code> and <code>void</code>. The rest is all done with two or three attributes and massive nesting.

blocks|key|1605335|text|在一个跨部门的政府项目中，我们必须向他们发送数据。他们听说xml是未来的发展方向，所以他们转而使用xml。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605336|他们一直说我们的xml不能正确解析。我们查看了我们正在生成的数据，它是有效的xml，因此我们询问问题出在哪里。|1605337|事实证明，他们已经编写了自己的解析器，该解析器计算空格，而我们的xml中有太多空格。|1605338|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

On an inter-department government project where we had to send data to them. They'd heard that xml was the way of the future so they switched over.

They kept saying that our xml wouldn't parse properly. We looked at the data we were producing and it was valid xml, so we asked what the problem was.

Turns out they had written their own parser, which was counting whitespace, and we had too much whitespace in our xml.

blocks|key|1605369|text|使用它存储极少量的数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605370|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Using it for tiny amounts of data.

blocks|key|1605388|text|apache配置文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605389|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

blocks|key|1390524|text|几乎所有用Java编写的东西都滥用它，或者使用它作为配置文件的格式来滥用用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390525|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Pretty much everything that's written in Java abuses it, or abuses the users by using it as a format for configuration files.

blocks|key|1390548|text|XMPP非常出色，因为它将整个通信会话编码为一个单独的XML文档。因此，不仅基于DOM的API在实现XMPP应用程序方面毫无用处(尽管对某些人来说，这是一个特性)，而且在缺少多线程的情况下，即使是SAX也是有问题的。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1390549|几年前，我就在这样的环境(单线程，使用SAX+)中实现了一个Jabber客户机；当套接字不再返回数据时，我必须对解析器进行修改，以便将控制权返回到应用程序级别。|1390550|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/Jabber^0|0|4|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

<a href="http://en.wikipedia.org/wiki/Jabber" rel="noreferrer">XMPP</a> is pretty egregious IMHO, because it encodes an entire communication session as a single XML document. As a result, not only are DOM-based APIs useless in implementing XMPP apps (though to some folks, I'm sure that's a feature), but even SAX is problematic in the absence of multi-threading. 

I implemented a Jabber client years ago in just such an environment (single-threaded, using SAX APIs); I had to make modifications to the parser to get control back to the application level when the socket returned no more data.

blocks|key|1390581|text|抨击XML的人--我想--没有意识到它出现之前的生活是多么可怕。每次要交换数据时，都必须详细地记录如何将数据编码为80列的文本。通常，前十列是元数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390582|然后双方都必须为它编写代码。|1390583|XML和模式的正确使用是指不需要编写、测试和调试的大量代码。|1390584|我不明白为什么当它被用来保存配置数据时，人们会讨厌它。这通常是一种很好的工作方式。我认为这里发生的情况是，配置本身是一个后遗症，人们错误地认为XML才是问题所在。|1390585|世界需要的是一个能够理解模式和CSS的好的XML编辑器。与XML相关的主要难题是必须使用普通的txt编辑器对其进行编辑。|1390586|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

People who knock XML - I think - don't realise how horrific life was before it. Every time you wanted to exchange data, you had to document in excruciating detail how it would be encoded into 80-column text. Usually the first ten columns or so would be metadata.

Then both parties would have to write code for it.

Proper use of XML and schemas is pages and pages of code that you don't have to write, test, and debug.

Beats me why people resent it when it's used to hold config data. It's often a great way to do the job. I think that what's happening here is that the config itself is a pain in the rear, and people are mistakenly thinking that it's XML that's the problem.

What the world needs is a good XML editor that understands schemas and CSS. The main pain relating to XML is having to edit it with a plain txt editor.

blocks|key|1390617|text|市场营销。认为说“我们制造Java+%2B+XML”就足以赢得一些付费客户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390618|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Marketing. Thinking that saying "We make Java + XML" is enough to get some paying customers.

blocks|key|1390659|text|使用SOAP传输XML文档，该文档只有一个包含编码数据的节点，解码后会得到一个一级深度的名称-值对XML。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390660|我是认真的。我在一个必须使用的API中处理了这个问题。|1390661|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Using SOAP to transport an XML document, that has just one node containing encoded data, which when decoded gives you a one-level deep XML of name-value pairs.

Seriously. I've dealt with this in a API I've had to consume.

blocks|key|1605601|text|编写您自己的XML解析器，这是我过去一直有罪的地方。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605602|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Writing your own XML parser, a sin of which I've been guilty in the past.

blocks|key|1390726|text|使用XML来描述UI可能不是最糟糕的滥用，但它仍然相当糟糕。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390727|我看不出引入一种新语言(每个XML模式实际上都是一种新语言，您必须学习特定的标记和属性)来完成普通的旧Java完全有能力完成的工作。此外，当使用Java语言(或任何常规编程语言)编码时，您可以访问标准的编程构造，如if和循环，并能够调用方法，为公共构造创建工厂等。|offset|length|style|CODE|1390728|在我看来，这适用于桌面和Web环境。例如，在JSP中，首先使用XHTML定义Web页面界面……我才意识到你毕竟需要条件和循环，也许还需要一些额外的编程逻辑。因此，人们添加了新的标记，如c:if,+c:forEach和“表达式语言”，因此最终只能使用XML语言进行编程，使用这种笨拙的结构，必须将其作为“标签库”引入。我越想它，它看起来就越糟糕:)|1390729|entityMap^0|0|2Z|2|0|2K|F|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|J|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|K|$]]

Using XML to describe UIs maybe isn't the worst abuse there is, but it is still pretty bad. 

I don't see a point in introducing a new language (and each XML schema is effectively a new language, with specific tags and attributes you'll have to learn), to do the job that, say, plain old Java is quite capable of doing. Furthermore, when coding in Java (or any regular programming language), you have access to standard programming constructs, like <code>if</code>s and loops, and ability to call methods, create factories for common constructs etc. Along with all other benefits from your IDE like call hierarchy, finding uses of method in workspace etc.

This is applicable, in my opinion, for both desktop and Web environments. For example, in JSP, you start by using XHTML to define your Web page interface... only to realize that you need conditionals and loops after all, and maybe some additional programming logic. So then people add new tags, like <code>c:if, c:forEach</code>, and an "expression language", so you end up programming in XML, with this awkward constructs, that have to be introduced as "tag libraries". The more I think about it, more awful it looks :)

blocks|key|1390773|text|由Microsoft+Integration+Services包生成/使用的XML。成百上千行代码--在一行中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1390774|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

the XML produced/used by Microsoft Integration Services packages. Hundred/thousand of lines of code - in one single line.

blocks|key|1605760|text|一些“开发人员”在做这件事(不，这不是有人在这里开的关于XML的有趣的笑话，这个人是真的)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605761|<binary>
++<byte+i="1">123</byte>
++<byte+i="2">99</byte>
++etc...
</binary>|code-block|syntax|javascript|1605762|我想当我看到这个的时候，我甚至气得满脸通红。像这样的人应该立即被解雇。|1605763|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Some "developer" doing this (and no, this was NOT the funny joke someone made here about XML, this guy was for real):

<pre><code>&lt;binary&gt;
 &lt;byte i="1"&gt;123&lt;/byte&gt;
 &lt;byte i="2"&gt;99&lt;/byte&gt;
 etc...
&lt;/binary&gt;
</code></pre>

I think I even had a red face from anger when I saw that. People like this should simply get fired instantly.

blocks|key|1605810|text|XAML。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605811|XML不是，也永远不应该是一种编程语言。|1605812|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

XAML.

XML is not, and should never be, a programming language.

blocks|key|1605849|text|数据(大约40个字段)存储为XML文件，然后xml文件存储在mysql中...我不明白为什么..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605850|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

data (about 40 fields) stored as XML files and then xml files stored in mysql ... I don't get it why ..

blocks|key|1605896|text|我见过(错误地)将XML用作PLSQL过程的参数格式(!)。输入参数的格式预期如下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1605897|<procedure>
++<parameter1>
++++<value1>
++</parameter1>
++...
</procedure>|code-block|syntax|javascript|1605898|返回值的格式类似于(eek!)|1605899|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I've seen XML being (mis)used as a parameter format for a PLSQL procedure (!).
The input parameters were expected to be in a format like this:

<pre><code>&lt;procedure&gt;
 &lt;parameter1&gt;
 &lt;value1&gt;
 &lt;/parameter1&gt;
 ...
&lt;/procedure&gt;
</code></pre>

And the return value was similarily formatted as a &lt;result&gt; (eek!)

XML has its uses.

What is the worst abuse of XML that you have seen? What about XML made it so unsuitable for the task?

What is the worst abuse of XML that you have seen?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

XML有它的用途。您所见过的最严重的XML滥用是什么？是什么让XML如此不适合这项任务呢？

问您所见过的最严重的XML滥用是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问您所见过的最严重的XML滥用是什么？EN