Таймер на платформе WPF

Static properties, particularly mutable ones, are generally discouraged in object-oriented programming due to several significant disadvantages related to testability, concurrency, flexibility, and code maintainability.
dogan-ucar.de
+2
The main disadvantages include:
- Difficult Unit Testing: Static properties create tight coupling between classes, making it difficult to isolate code for testing. Since static members belong to the class itself and not an instance, they cannot be easily mocked, stubbed, or replaced with test doubles (fake implementations) in a test environment, which hinders the use of dependency injection.
- Global, Mutable State: Static properties often introduce global state into an application, which can be modified from anywhere in the codebase. This makes the application's state unpredictable, leading to unexpected side effects, bugs that are difficult to trace, and a general lack of control over how the property is used.
- Concurrency Issues (Not Thread-Safe): In multi-threaded environments (like web applications), multiple threads can access and modify the same static property simultaneously. This leads to race conditions, inconsistent data, and unpredictable behavior unless explicit and careful synchronization (like locking) is implemented, which adds complexity.
- Reduced Flexibility and Extensibility: Static properties cannot be overridden, participate in polymorphism, or implement interfaces. - This makes it hard to change or extend their behavior in subclasses without a complete rewrite of the class, limiting the ability to adapt the code to future requirements (e.g., if you initially only need one of something, but later need two with different configurations).
- Memory Management and Leaks: Static variables remain in memory for the entire lifetime of the application or process (until the application domain unloads), as they are rooted by their class type and not subject to typical garbage collection cycles based on object scope. If they reference large objects or data structures that accumulate information (like caches), they can lead to memory leaks and increased memory usage.
- Breaks Object-Oriented Principles: Heavy reliance on static members is often considered an "anti-pattern" that moves away from the core tenets of object-oriented design, such as encapsulation, making the code less modular and cohesive.
Stack Overflow
+10
Appropriate uses for static properties are generally limited to truly application-wide, unchanging data like constants (e.g., Math.PI or configuration settings that don't change at runtime) or when implementing specific patterns like the Singleton pattern with careful consideration for its drawbacks.
Software Engineering Stack Exchange
+2