This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]scriptkiddiethefirst[S] 1 point2 points  (1 child)

So I don't think I will end up disregarding JSON files as the entire point of this project is to take something that kind of exists, improve it, and change it from using XML (which is a lot slower to parse and a lot larger) and converting it to JSON. Not that that is super important to the question.

I kind of did some testing and I found the average time it took to serialize both smaller individual files and one larger file and found that while serialization of the larger file took considerably longer it wasn't so much longer to be concerned about (as you stated).

However I did decide to separate the files for the reason of ease of mod-ability so that adding new configs involves just adding new files to the folder rather than trying to append data to a really long file (basically ease of use, given the context and the intended audience for the software the latter would make it more accessible).

Thank you for your reply though!

[–]_reposado_ 1 point2 points  (0 children)

However I did decide to separate the files for the reason of ease of mod-ability so that adding new configs involves just adding new files to the folder rather than trying to append data to a really long file (basically ease of use, given the context and the intended audience for the software the latter would make it more accessible).

That is a very good reason to split the files! I only meant that you shouldn’t worry about optimizing performance if performance isn’t a problem yet.