07-25-2022 10:00 AM
@Frozen wrote:
Your question in the first place makes me think... if the speed of data conversion to xml (or JSON) is an issue, you might have bigger problem... either coding or architecture.
This was similar to my first thought which was "Is speed of reading a file really that big of an issue? Are we optimizing for something that doesn't really matter?" After all, a configuration file should not be constantly read.
Now there are other reasons to possibly move to JSON:
1. A lot more human readable (my opinion)
2. More open of an architecture
3. The JSONtext library by JDP Science!!!
I am a HUGE fan of the JSONtext library (available through VI Package Manager). One of the big benefits is it is smart enough to handle changing of your data formats (JSON file written in format 1.0 can still be read and populate into format 2.0). This is a much more important benefit than the reading and parsing speed of the file.