Content
@
0 reply
0 recast
0 reaction
Ryan J. Shaw 🎩
@rjs
@chrisdom insulted my beloved .NET and I couldn't let it stand. Turns out the original article made 2 mistakes, of course: (1) they used peak memory rather than allocations and (2) they used `Task.Run`, which schedules a threadpool thread to run unnecessarily. I modified the original benchmark to use a proper benchmarking tool (BenchmarkDotnet) and I removed `Task.Run` (for practical reasons, I switched to a 1s delay instead of 10s). Result: without `Task.Run` there's a 57% reduction in memory usage and .NET's memory allocations beats Rust by about 15%.
5 replies
0 recast
16 reactions
Chris Dom
@chrisdom
i'm sure if we use the "proper" benchmarks for each language, like BenchmarkGo BenchmarkRust BenchmarkDeez, they'll come out #1 too
0 reply
0 recast
1 reaction
Ryan J. Shaw 🎩
@rjs
Let's just hope for /frametrain 's sake that I'm right and the guy who went on to design & core develop Typescript after C# knows what he's doing 🙃
0 reply
0 recast
1 reaction
Chris Dom
@chrisdom
touché 😆
0 reply
0 recast
1 reaction
