2 ms·
Is it though? Why not just use code (generated if required) to read xml or json for each class? That way it is clear, in the source code and can perform other
by grey-area 6y ago
Is it though?
Why not just use code (generated if required) to read xml or json for each class? That way it is clear, in the source code and can perform other transformations as required.
- masklinn 6y ago> Is it though? Yes. It's what the Java world was before annotations became a thing. > Why not just use code (generated if required) to read xml or json for each class? Because it didn't happen that way, because Java is way too verbose for that, and because "imperative declarations" are a horrible thing.
- grey-area 6y agoYou're describing what was, not what could have been. There's nothing to preclude just having a function on your classes to read from json or db data. Perhaps the culture is stronger than the language though.