Hynad said:
JWeinCom said:
I understand your definition. We can certainly choose to use that definition. Or we could define it based on how much the end product differs from the original. I'm asking why you think your definition is more useful. Do you have anything better than because I said so?
|
Because nothing is left to interpretation and is consistent. Unlike the one you and Shiken are throwing around.
|
Sure. That's a valid point, assuming we can always tell whether or not the same source code is used. But while focusing only on one factor makes things easier, it makes classification systems less useful.
For example, when we're dealing with animals, we classify using multiple traits. Some traits of mammals are that they have fur, that they produce milk, and that they give birth to live children.
Now, let's take the platypus as an example. If we decided to focus solely on one factor, does it give birth to live offspring, we would say, no not a mammal. Nothing would be left to interpretation and perfectly consistent.
On the other hand, if we take all the factors into account, then we can classify the platypus as a mammal. It's less consistent (there is still debate over how to classify the platypus) but it allows us the ability to take more factors into consideration and put the platypus where it makes most sense, because it shares more traits with mammals then it does not.
We can think of Xenoblade Remastered as a platypus. It has one factor in common with FFVII remastered. Same source code as the original (I'm assuming). But, it has other factors that are more in common with other remakes like Link's Awakening. Added content, new artstyle, new music, mostly new assets, etc. I think a classification system that incorporates these factors is preferable to one that does not.
If you want consistency to be the be all end all, then your system is clearly better. I'd argue that categorizing things that are more similar together is much more important, and I think Shiken's definition does a way better job of that.