frameworkagnosticism
Framework-agnosticism is a software design stance in which code and architectural decisions are made to avoid dependency on a specific framework, library, or platform. The goal is to create components that can be used across different environments or wired into multiple frameworks with minimal modification. This often involves defining stable interfaces and keeping framework-specific concerns isolated.
Practice considerations include portability, testability, and ease of migration. Benefits include reduced vendor lock-in, simpler experimentation
Techniques commonly employed are dependency inversion and inversion of control, explicit interfaces or ports, adapters, and
In practice, framework-agnostic code is often balanced with pragmatic use of framework features where they provide