Property comparison is useless in effect if we’re both thinking of the same thing here, but regular property comparison can be done without this module: (foo.Property == baz.Property) And about ‘property copying between different classes’ I genuinly fail to see a case where that’s useful, you can substitute direct class mutation with composition or even inheritance, which you should already be using anyway.
And about Instance serilization, serializing the entirety of an instance is not useful, like I said earlier many use cases you could argue this module supports may likely be redundant because it’s such a niche feature, you should only be serializing what you need to store, storing entire instances does not come cheap especially with how garguantuan the roblox API is already.
in this case Roblox not implementing :GetProperties after many years of asking.
I wonder why? Why do you think attributes are only exposed through :Get() and :Set() methods? Directly mutating properties was likely unfeasible, I doubt property access is as rudimentary as you think it is…
Although, yeah I guess the OP could be indexing a dictionary instead of a bunch of if statements but idrc as long as it works well, I don’t think the performance gain is worth the effort.
“All of this just works!” jokes aside, it’s not about performance, that’d be very micro. As I mentioned it’s about scalability and cleanliness here.