3 ms·
Usually, when .net is really slow, the cause has been that I'm using a Microsoft library 'wrong'. The solution has been to learn how that library works internal
by shubb 10y ago
Usually, when .net is really slow, the cause has been that I'm using a Microsoft library 'wrong'. The solution has been to learn how that library works internally, and work around it, rather than runtime level optimizations.
Although this is all good stuff to know, if you are here trying to fix your applications performance problem, this is probably the wrong tree to bark up.
- recursive 10y agoAre you talking about things like using List<T>.Contains() instead of HashSet<T>.Contains()? I've been doing .net for some time, and your comment is not consistent with my experience.
- jackmott 10y agoProgramming is a very varied field. Sometimes people forget that their coding experience can be totally different than anothers. Consider someone trying to do a 3D game in C# vs a web application back end. The kind of performance pitfalls they run into will have no similarity.
- recursive 10y agoThat's totally true. For instance, I (almost) never think about garbage collection. For some kinds of development, I suppose not accounting for it can cause a complete failure.