_You_ may think it's fun to work with, and I guess it depends on what you think is fun (programming in Chef sounds fun, but is it pragmatic for what you're doin

_You_ may think it's fun to work with, and I guess it depends on what you think is fun (programming in Chef sounds fun, but is it pragmatic for what you're doing?). And here's my comment to another comment on the blog post: The question is not whether you've used C# extensively and think it is pragmatic, but whether you have used anything better (e.g. Common Lisp) and _still_ think it's as pragmatic you once thought it was. If you say that C# is more pragmatic than, say, using COBOL for an web application, then sure. But the author of this post is correct insofar as new C# features sound a lot better on paper than how they really stack up when wanting to express yourself in code. Not to even mention that if you go outside of the OOP/procedural paradigm in C# and start coding using functional-style language constructs, C# gets pretty ugly pretty fast.