Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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

75%
+4 −0
Q&A What are the disadvantages of using static methods in Java?

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: ...

posted 3y ago by Alexei‭  ·  edited 3y ago by Alexei‭

Answer
#2: Post edited by user avatar Alexei‭ · 2021-09-19T05:40:20Z (about 3 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 user avatar Alexei‭ · 2021-09-19T05:39:46Z (about 3 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.