• 0 Posts
  • 83 Comments
Joined 2 years ago
cake
Cake day: January 5th, 2024

help-circle







  • Yup, that’s my interpretation too. It just doesn’t sit well with all the other operators.

    All the others are phrased as direct questions about the values of A and B:

    • A AND B = “Are A and B both true?”
    • A OR B = “Are either A or B true, or both?”
    • A NAND B = “Is (A AND B) not true?”
    • A IMPLIES B = “Is it possible, hypothetically speaking, for it to be the case that A implies B, given the current actual values of A and B?”

    You see the issue?

    Edit: looking online, some people see it as: “If A is true, take the value of B.” A implies that you should take the value of B. But if A is false, you shouldn’t take the value of B, instead you should use the default value which is inexplicably defined to be true for this operation.

    This is slightly more satisfying but I still don’t like it. The implication (ha) that true is the default value for a boolean doesn’t sit right with me. I don’t even feel comfortable with a boolean having a default value, let alone it being true instead of false which would be more natural.

    Edit 2: fixed a brain fart for A NAND B









  • You complain about ASCII filenames but a few of the examples are obviously Unicode, namely using emoji, well outside of the ASCII character set. But since you’ve brought up Unicode file names, let me introduce you to bidirectional text!

    If you use Hebrew or Arabic, some of your directories or files will have right-to-left text in them. This is a recipe for disaster.

    If in English you’d have “C:\Users\Adam\Documents\Research\Paper.pdf”, which breaks down to:

    1. C:\
    2. Users\
    3. Adam\
    4. Documents\
    5. Research\
    6. Paper.pdf

    In Hebrew you’d have: “C:\משתמשים\אדם\מסמכים\מחקר\מאמר.pdf”, which breaks down to:

    1. C:\
    2. משתמשים\
    3. אדם\
    4. מסמכים\
    5. מחקר\
    6. מאמר.pdf

    The entire path goes backwards, and the “.pdf” extension is visually attached to the “Users” folder if the text is rendered naively. It’s insane. Fortunately many GUI shells nowadays separate each path item so they can’t get intermixed like this. Example:

    But still, if you copy a path into plaintext, it will still visually look wrong, and there is literally nothing that anyone can do about it. This is the correct way to render this text.

    Exact same issues occur in Arabic and the few other RTL languages usedin the world. It’s a massive pain.

    Edit: oh, and on commandline on Windows, the required characters aren’t even available by default so you get this lovely thing