Search results for query: *

Thank you for the explanation! I now have a much clearer understanding of the design philosophy behind VaM’s .var packages.

Thank you for clarifying the design rationale! I agree that prioritizing filename parsing for efficiency—especially given how rarely most users modify .var files—is a pragmatic approach. The balance between performance and usability for the majority of users makes a lot of sense. From a purely...

I agree with the point that Human sloppiness is something that no format can solve, :LOL::LOL::LOL:. Generally speaking, in my conception, filenames are very easy to modify. Because it's a normal operation for users. Moreover, VAR files are very accessible to users. So I'm actually quite...

My inquiry is purely driven by curiosity about the design rationale behind the current structure of VAR files. As I expressed earlier, what puzzles me is why this system appears to embed significant metadata directly in filenames (like version numbers), rather than storing it internally as...

Why does the structure design of meta.json in the var package not include version? Why does the filename {CreatorName}.{PackageName}.{Version}.var use the original author's name for CreatorName, rather than a transformed name (e.g., spaces converted to underscores)? This confuses me. It seems...