4 ms·
How would we prevent this? Asking for a friend.
by stephengillie 9y ago
How would we prevent this? Asking for a friend.
- cutler 9y agoJust refuse to play the insane Java/C# Enterprise OO game. Kotlin would be a good alternative but my preference would be Clojure where brevity and simplicity are valued.
- BoorishBears 9y agoOr 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.
- solotronics 9y agopersonally I find Java EE nauseating
- user5994461 9y agoDon't prevent them, encourage them. The next guy who work on your code will be happy to have variable and class names longer than 3 characters. Short names are evil.