Frameworks are known to limit default functionality. Is this generally considered a benefit or a disadvantage?

• A. Benefit
• B. Disadvantage
• C. Neither
• D. Both

Answer: (B)

Frameworks impose defaults to provide structure, consistency, and safer starting points. That guidance, while helpful for common cases, also restricts what you can do without extra work. When a project needs a non-standard feature or a highly customized behavior, you often have to fight the framework’s conventions—adding boilerplate, overriding defaults, or writing more complex code—to achieve it. That additional effort and potential clash with the framework’s patterns make the limitation a drawback in many scenarios. The upside is the speed and reliability you gain for typical needs, but overall, limiting default functionality is generally seen as a disadvantage because it reduces flexibility and raises the cost when unique requirements arise.