I think the fact that nobody on the GitHub discussion recognized that it was an issue with not respecting locale settings, and not some Windows specific problem, illustrates my point.
If I hadn’t spoken up by starting this post on Discourse, it likely would have only been fixed for Windows, and only
strftime and not
Bugs usually happen for reasons, whether it be typos, off-by-one issues, confusable names, and for strings it’s often encoding / indexing issues, and in this case it seems, a lack of awareness of locale related issues.
Just sweeping it under the rug by saying “it’s just a bug” means that people won’t go and check for other places where there might also be bugs due to similar issues.
(I note that there was one earlier with BigFloat formatting discussed recently, with locales that swap
, from the American meaning).
Finally, this is in no way meant as denigrating other people or their work, not that many people are aware of all the issues with dealing with locales, national character sets, encodings, conversions, collation, security, etc.
(just as I am not aware of all of the issues behind the heated discussions of dot vs. inner, adjoint vs. transpose),
and also many people simply aren’t that interested to dig into them (they have enough on their own plates with all the great stuff going in the Julia ecosystem (like all the compiler optimizations, or the new packaging system, for example! )
We all have different areas of expertise, this just happens to be one of mine.
I hope you recall that I’ve always acknowledged the brilliance of all of the Julians I’ve met,
(and you’ve managed to hire quite some of the cream of the crop at JC!), so please stop taking any discussion of bugs, different approaches to string handling, etc. as being “swipes” or “attacks”.