An idea for Myth II - A modification to tags
Parsing XML is a very CPU intensive computation, compared to parsing binary-tag formats like Myth does currently. Considering tags are there for Myth to read them, not for users to read them, and that editors exist for these already, there is no reason to convert it to XML.
Also, XML is a very disk-space inefficient format. For example, in a binary file, value 12345 stored as a 32-bit integer would take exactly 4 bytes. In XML, it would be something like ... for a total of 40 bytes. A 10x increase. XML makes sense for some things, such as configuration files, but not all of Myth's data files, which would make Myth slower and take up more HD space with no added benefit from the changes.[/color]
Edited By Myrd on 1112896809
Also, XML is a very disk-space inefficient format. For example, in a binary file, value 12345 stored as a 32-bit integer would take exactly 4 bytes. In XML, it would be something like
Code: Select all
<MonsterVitality>12345</MonsterVitality>
Edited By Myrd on 1112896809