3 ms·
> Now Go loses by over 13 times to the winner. It also loses by over 2 times to Java, which contradicts the general perception of the JVM being a memory hog and
by Mawr 2y ago
> Now Go loses by over 13 times to the winner. It also loses by over 2 times to Java, which contradicts the general perception of the JVM being a memory hog and Go being lightweight.
Well, if it isn't the classic unwavering confidence that an artificial "hello world"-like benchmark is in any way representative of real world programs.
- phillipcarter 2y agoYes, but also, languages like Java and C# have caught up a great deal over the past 10 years and run incredibly smoothly. Most peoples' perception of them being slow is really just from legacy tech that they encountered a long time ago, or (oof) being exposed to some terrible piece of .NET Framework code that's still running on an underprovisioned IIS server.
- fulafel 2y agoAlso of course Java and C# overwhelmingly use threads and not async for this kind of thing.
- neonsunset 2y agoVery few .NET projects rely on explicit threading. There is almost never a reason to do so when tasks can be used instead, like in this benchmark.