2 ms·
It doesn't have to be a class. It can be an interface. And regardless of what it is, it has to go somewhere. Whether it's in assorted_functions.c or Permissions
by elric 11mo ago
It doesn't have to be a class. It can be an interface. And regardless of what it is, it has to go somewhere. Whether it's in assorted_functions.c or Permissions.java makes little difference.
I mean it makes sense to group "like" things together. Whether that's in a module, a class, an interface, or a namespace. Having a huge number of things globally is just confusing pollution.
- javcasas 11mo ago> it has to go somewhere Yes, but going as a static method into a class that goes into a module is overkill vs just putting it in the module. > Having a huge number of things globally is just confusing pollution. I don't know what language you use, but modern programming languages allow specifying what to import when importing a module. You don't have to import everything from every module.