3 ms·
C#'s object model is so good they created dynamic so that people don't have to use it...
by Touche 11y ago
C#'s object model is so good they created dynamic so that people don't have to use it...
- moron4hire 11y agoOnly people who don't use C# regularly think `dynamic` is something C# programmers use regularly.
- earlz 11y agoThis 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.
- moron4hire 11y agoWell, to be fair, a lot of those got started back in the pre-generics 1.1 era, and the rest are designed to have a similar interface.
- deleted 11y ago[deleted]
- Zergy 11y agoAdding a new tool to swiss army knife doesn't indicate the other tools are dysfunctional, it just means that additional functionality was needed.
- SneakerXZ 11y agoThey created dynamic to improve COM interfaces and bridging to other languages.