3 ms·
>without much performance problems. Just depends on the kind of thing you are working on. For many people you could use dynamic all over, no problem. For many
by gameswithgo 8y ago
>without much performance problems.
Just depends on the kind of thing you are working on. For many people you could use dynamic all over, no problem. For many people that would be a disaster. (super high throughput server, things that need super low latency, games, rendering, libraries that could be used in any of those domains)
- joshschreuder 8y agoFrom personal experience it also gets abused by people looking for ways to shortcut writing actual classes
- tluyben2 8y agoExactly: I am usually writing backends for financial systems which need high throughput and low latency; dynamic is just a massive performance hit. And almost never needed; people usually use it because lazy in my experience. It is just ‘faster’ for people to dump JSON into dynamic and write against that than it is to properly create structured classes. In the end ofcourse the unittests validate the JSON, the code is slow and harder to use and refactor; you would have saved time and stress actually just writing classes with proper typing.