@0xC0000022L They also take them into account when doing things like string equality comparison. Yeah, at a lower level that isn't how they're stored... but in the case of Elixir, I'd almost guess that was inevitable because they wanted to maintain compatibility with Erlang, which had already decided how to store strings. I haven't looked too closely at Swift, but I imagine they are going to be the same, because they wanted to interoperate with ObjC.

@0xC0000022L Swift and Elixir at least, but probably even more by now.

I don't know about the rest of you but on my Mac, AWT's file chooser looks pretty much like the real deal and AWT buttons look a lot more native than Swing ones.

The problem I have at work is that I often run into warnings which someone else suppressed because they didn't understand what it was saying. So I guess whether a warning has merit is a subjective matter. :/

I guess a bit of time passed, and now we have a couple of languages which actually do this. :D

I tried searching the local (Australia) giant hardware store's web site and the first hit for "painting tape" is a product labeled as "masking tape", so I guess that's that. ;) Good old terminology differences between regions, I suspect. People are really picky about what counts as gaffer tape as well, depending on where they live.

Maybe in Poland they experience the problems so frequently that they have simply gotten used to it. In English stuff, it makes me cringe every time I see something like "item(s)". Our Arabic translation has similar dodgy stuff going on, and it's one of the things which Crowdin detect as a potential problem - translation contains some punctuation when the original didn't.

"Why the hate for JSON?" No support for human-readable comments, crap escaping of Unicode, and a weird syntax requiring me to quote the keys even though they never contain whitespace. Plus the usual inability to extend things because nobody thought about namespacing... by the time you resolve that one, you end up with something that looks even worse than XML did in the first place, all for what, the benefit of avoiding some angle brackets?

So we're saying we can ignore Polish plurals because they could reorder the entire thing to put it in a place where the plural isn't necessary, I guess.

I guess you also have to worry about languages which might use a completely different character set to format numbers for formal documents, like 大字 in Japanese.

The most amusing thing I think about this answer is the implication that we have some kind of product owners, or people who know the requirements when they file the tickets. How much easier would software development be if this were the case! lol... Not saying the answer is bad, though.

@Ӎσᶎ becauseit'sveryhardtoreadthingswhentheyaremashedtogetherwith‌​nospaces (and with hex, usually groups of 2 or 4 digits.)