Some functional constructs isn't really what I was talking about. The premise of the article (full disclosure, I only made it partially in, so correct me if I'm wrong) seemed to be "here's how you can program with almost nothing but static methods". That's definitely counter to mainstream usage, it's attempting to use C# as if it were a non-OOP language, and that's going to frustrate anyone new to the codebase.