re: Sometimes, the elegant implementation is just a function VIEW POST

re: Could you elaborate? In Java, at least, a common pattern is to make "Utils" classes, which are usually singleton or non-instantiable classes that j...

First, let me agree that in Java, and C#, a class with static methods is the correct approach.

What I lament is that the language forces you to do this. They have packages/namespaces which should be used for this purpose. A class is meant to represent an instantiable type, if you have only statics in it it violates this definition. That is, I'm complaining the languages are creating confusion as to what a "class" is.

Ah I see. The Utils pattern really does fly in the face of OOP, doesn't it?

I understand that you see this as a problem, conceptually. In practice in Java, you could statically import the class and use the methods like functions. In that case, the class would ask more like a namespace than a „true“ OOP class.

code of conduct - report abuse