Hacker News new | ask | show | jobs
by antimagic 4207 days ago
I find posts like this nearly entirely lacking in interest. There was so much attitude and not near enough actual analysis. A much stronger post would have actually disassembled the resulting code in each of the different configurations, and looked to see why the various permutations had the performance that they did. We would then have a much stronger understanding of where Swift's performance is at, instead of looking at a series of not exactly equivalent benchmarks that leave us wondering if we're not just seeing an artifact of the differences in the benchmark code as opposed to differences in real-world performance.

I for one would not be changing my approach based on this post. I might start doing some disassembly if I was writing performance sensitive production code in Swift, but that would be about it.