This is true, but I've seen libraries that lazily use dynamic in their API instead of properly implementing things with generics to accomplish things. Also, th

This is true, but I've seen libraries that lazily use dynamic in their API instead of properly implementing things with generics to accomplish things. Also, the way the various Microsoft frameworks use strings to specify property and type names drives me insane. It's just like.. "Hey, we have a really nice type and generics system... but here lets hop around that and instead use strings that we hope you never need to refactor, as well as magic method names (ie, RegisterRoutes, Application_Start)". This seems to be getting a little better, but it's still way too prevalent. It's almost like the people responsible for writing C# frameworks had a disagreement over strict typing and decided to just contaminate a ton of APIs to spite the type system.