Corner cases like `prod([Int8(100), Int8(100)]) != prod((Int8(100), Int8(100)))`? Both returned integers, but the left was 10000 while the right was 16. [0] Wh

Corner cases like `prod([Int8(100), Int8(100)]) != prod((Int8(100), Int8(100)))`? Both returned integers, but the left was 10000 while the right was 16. [0] Which, apparently, sat in the standard library for almost four years after it was introduced before it was fixed. [1] Even if there was some merit to your argument, I would still find the attitude disqualifying. While it may be technically true that all programming languages have bugs, software and software communities for numerical computing should take responsibility and treat those bugs seriously, not downplay them by pointing to the fact that other software probably has bugs too. FWIW I don't have a horse in this race. I've used both before, and I currently make money using neither. I liked Julia. I find that article concerning. And I find the attempts by Julia users to discredit that article in this thread, without addressing its substance, even more concerning and disappointing. Well, bugs can be fixed. But ideally not by a culture that dismisses them as inevitable or unimportant. [0] https://github.com/JuliaLang/julia/issues/39183 https://github.com/JuliaLang/julia/issues/39183 [1] https://github.com/JuliaLang/julia/blob/26f2333686ce90331548035d47ec707227efb417/base/tuple.jl#L311-L317 https://github.com/JuliaLang/julia/blob/26f2333686ce90331548...