3 ms·
> assuming that one of the most widely used runtimes in the world had easy optimizations to do, about 20 years after it was first launched. Perhaps not trivial
by jen20 6y ago
> assuming that one of the most widely used runtimes in the world had easy optimizations to do, about 20 years after it was first launched.
Perhaps not trivial, but it did have easy optimizations - within hours of it being open sourced, external people who had not worked on the codebase were making pull requests with straightforward (and in some cases substantial) optimizations. Matt Warren (author of Benchmark.NET) has tracked many of these.
- oblio 6y agoYeah, but those happen in any code base. You can always find improvements, sometimes changes that seem trivial in hindsight. That doesn't make the original code base crap :-)
- jen20 6y agoYup - absolutely agree. Being open source and accepting contributions means that people can spend time on bits which otherwise will not get prioritised.
- philliphaydon 6y agoWhen Microsoft worked on the .net framework. Performance was not a metric they used. The only performance goal they had was basically “it can’t be slower than it is now”. So performance can’t regress. Since open sourcing performance is one of the goals in mind. And it shows.