Why do some say the "Builder Pattern" is better than using Extension methods for Fluent interfaces?
builder, c#, extension-methods, fluent
Solution
This SO Question describes disadvantages of extension methods.
Furthermore some think, that extension methods violate the Open/Closed principle rather than following it, because they introduce features in a way that may have not been intended by the original creator.
If Builder Pattern achieves the same goals without disadvantages, then why not use it instead.
Problem
In this discussion (creating API that is fluent ) , a response indicates that the Builder Pattern is better than using Extension methods for creating Fluent interfaces. What are the reasons this could be true? Extension methodology follows the "O" in the SOLID principle... I personally only use Extension methods for developing Fluent interfaces but am wondering if I need to rethink this...