Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
I am not a Java developer, but a C# .NET one, but I guess static concept is very similar between the two. As in many areas, it depends, but for most applications using static should be avoided: ...
Answer
#2: Post edited
by
Alexei
·
2021-09-19T05:40:20Z (over 2 years ago)
minor fixes
I am not a Java developer, but a C# .NET one, but I guess static is very similar between the two.- As in many areas, it depends, but for most applications using _static_ [should be avoided](https://medium.com/att-israel/should-you-avoid-using-static-ae4b58ca1de5):
- - Single Responsibility Principle violation
- - prevents polymorphism
- - prevents abstraction (cannot use in an interface)
- - prevents inheritance
- - **makes automatic testing through mocking way more complex and tedious**
- - prevents garbage collector to kick in and collect the memory
For the specific case of utility functions, static is very useful, but for a medium or large application this is only a tiny part of the codebase.
- I am not a Java developer, but a C# .NET one, but I guess **static** concept is very similar between the two.
- As in many areas, it depends, but for most applications using _static_ [should be avoided](https://medium.com/att-israel/should-you-avoid-using-static-ae4b58ca1de5):
- - Single Responsibility Principle violation
- - prevents polymorphism
- - prevents abstraction (cannot use in an interface)
- - prevents inheritance
- - **makes automatic testing through mocking way more complex and tedious**
- - prevents garbage collector to kick in and collect the memory
- For the specific case of utility functions, static is very useful, but for a medium or large application,[]() this is only a tiny part of the codebase.
#1: Initial revision
by
Alexei
·
2021-09-19T05:39:46Z (over 2 years ago)
I am not a Java developer, but a C# .NET one, but I guess static is very similar between the two. As in many areas, it depends, but for most applications using _static_ [should be avoided](https://medium.com/att-israel/should-you-avoid-using-static-ae4b58ca1de5): - Single Responsibility Principle violation - prevents polymorphism - prevents abstraction (cannot use in an interface) - prevents inheritance - **makes automatic testing through mocking way more complex and tedious** - prevents garbage collector to kick in and collect the memory For the specific case of utility functions, static is very useful, but for a medium or large application this is only a tiny part of the codebase.