• BatmanAoD@programming.dev
    link
    fedilink
    arrow-up
    3
    ·
    1 year ago

    I’m not sure I’d consider that “failing”. At first glance, I don’t mind the distinct “m” glyphs being juxtaposed. But perhaps I’d find it annoying after a while.

    • codemonk@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Maybe ‘failing’ is too strong. What I mean is that in situations like the one I showed, texture healing cannot solve the problem of uneven texture. Not that they claimed it does. It just eases the problem. I like to know the trade-offs. When does it provide an improvement and when not? What tensions does that create?

      From a users point of view, I do not know if it ‘fails’ or not. I totally agree with you. Maybe the I would find to distinct ‘m’ glyphs annoying, maybe not. And example emphasizes the ‘problem’. Maybe, I woukd even notice while coding or writing. To know that, I need to try. I just like to know the trade-offs in advance.

      • BatmanAoD@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        When reading the announcement post, I was indeed hoping they’d include an example word with two "m"s in a row, so I was glad to see the example here. I don’t mind it, but it does feel almost dishonest to exclude that case from their post.

        • codemonk@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          Yeah, I am always happy if a project not only mentions where it shines but also where it does not. But it is common practice not to do so. Same in academic publishing. Everybody is focused on selling oneself, it seems.