I have never been a fan of XML, I've hated it from "day one", the format is too inefficient, too bloated; I have had some ideas on things that can be done to reduce the size on xml data sets, such as having some kind of header definition embedded at the top of the file and other ideas, but the point of this post is not to talk those ideas, but rather my own proposal to start getting rid of xml.
One area where I find particularly painful to use XML is on configuration files and my proposal to fix this problem is to formalize a new format, which I call JINI for now. JINI is a subset of JSON similar in simplicity to the good old .ini files and it's used specifically for configuration purposes to replace all those app.config xml configuration files
Benefits
- Simple
- No brackets
- Simple
- Shorter
- Easier to read
- Simpler
- Everything that can be expressed in XML, can be expressed in JINI, but simpler
Too bad "jini" is kinda already taken (2 million results on Google and 714K on Bing say so)
I thought someone would have come up with this idea already, but a quick search gave me nothing, so I thought I would get the ball rolling
what do you think?
One area where I find particularly painful to use XML is on configuration files and my proposal to fix this problem is to formalize a new format, which I call JINI for now. JINI is a subset of JSON similar in simplicity to the good old .ini files and it's used specifically for configuration purposes to replace all those app.config xml configuration files
Benefits
- Simple
- No brackets
- Simple
- Shorter
- Easier to read
- Simpler
- Everything that can be expressed in XML, can be expressed in JINI, but simpler
Too bad "jini" is kinda already taken (2 million results on Google and 714K on Bing say so)
I thought someone would have come up with this idea already, but a quick search gave me nothing, so I thought I would get the ball rolling
what do you think?
