4 ms·
Or just don't be redundant in any language. Unless there are multiple types of a "SerializationProvider", the name could be shortened to "ProtobufSerializationP
by BoorishBears 9y ago
Or just don't be redundant in any language. Unless there are multiple types of a "SerializationProvider", the name could be shortened to "ProtobufSerializationProvider"
And if there are multiple types of "SerializationProvider" (ie. there's an unrelated "CachingSerializationProvider ") then the name is unfortunately long, but accurate
- smnplk 9y agoI think the main problem is not in the name of that class, the name is just a side effect of a bigger deeper problem.
- BoorishBears 9y agoWhat problem? DI is really useful if you're pragmatic about it, misuse is not really a property of a particular language
- 6ue7nNMEEbHcM 9y agoIt looks like they may have convention to put name of the base class/interface in the type name.