Hi. I've been thinking about the impact on overall Opus performance of storing persistent variables (Lister, script, etc) that potentially could become very large overtime.
One specific case: I'm considering extending TabRescue so it can do more than just reopen paths (restoring focus, selection, etc). Since the number of entries depends entirely on the user, would it make sense to store that data in separate files instead of letting Opus handle it internally?
I’m intrigued by the fact that a variable can grow very large when saved as text (searching in the forum about it I saw someone mention reaching a considerable filesize just from variables). Could that have any negative effect on Opus performance?
The same concern applies to script variables, which all get written into the same file. I imagine that if a script starts saving bigger and bigger variables, it might affect the performance of other scripts as well. Please correct me if I'm wrong.
Personally, I like how Opus has implemented variables, since it simplifies loading or saving a variable for the end user. I'd like there to be some support for saving variables in a separate file—if, of course, giant variables can have a negative effect.
