Home/ Questions/Q 6344079
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-24T20:34:07+00:00

If I have to design a Utility class( such as ByteUtils or StreamUtils or

  • 0

If I have to design a Utility class( such as ByteUtils or StreamUtils or StringUtils), what is the best design choice for them.

  • Should they be static classes (as I won’t have any states to store)
  • Should they be non-static classes ( so that if the objects are not used, they will be gc’d)

PS: By static class, I meant a class with static methods(and not the inner static class)

Please give advice on design choices for this ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If it is a general purpose utility, static is IMO better. You stated that you will not have any states to store, so I don’t see why should you make it non-static. Declaring it to be static will save memory too.

    • 0