xyz Although my initial question was about loading data speed (which seems to be about the same), @Toxe suggested it's important to consider how I would edit the data and @REVBENT said changing data in the script had no effect on performance in his tets, which made me consider what would be faster for the rest of the process.
And I'm focusing of optimization because I want to learn for bigger projects. But also, I have a pretty old PC and I would like my game to run fast in a lot of devices.
We need a description of the problem, not what you tried so far or how you think it should be done.
Makes sense. My initial problem was: "Given that a container will hold all the data from a match, even other containers like itself. What is the fastest way of loading this data (knowing that you won't need all the data at first, just a few initial elements) while ensuring that the iteration process will be fluid in as many devices as possible".
But I think it was answered since Dictionaries also need to initialize their content (for example, if a dictionary has a "myKey": CustomResource.new() it would need to initialize the CustomResource and its variables, including other internal resources. So in theory, there should be no difference between a dictionary and a Resource, unless initializing the base classes (like Object and RefCounted) took too long.
