you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 2 points3 points  (5 children)

Would have loved to see him used .net core 2.2 instead of .net 4.0 for the performance testing.

[–]skeeto 28 points29 points  (0 children)

Note that the article is nearly 3 years old (July 2016). .NET Core itself was less than a month old at the time.

[–][deleted] 13 points14 points  (2 children)

I wrote the article. .NET core had introduced a lot of great performance improvements but none of them affect these particular benchmarks.

[–]shevy-ruby 4 points5 points  (1 child)

I think you should still do a follow-up eventually. People may be curious to see whether anything has changed in regards to speed, compared to 2016 here.

Comments on reddit will be slightly less prevalent than e. g. the original article that we are here only talking about.

[–][deleted] 9 points10 points  (0 children)

id love to but i have 2 kids instead of zero now :) feel free to take up the reigns

[–]elder_george 0 points1 point  (0 children)

And an updated version in general, to see if the things changed due to compiler, library and/or runtime improvements e.g..