4 ms·

Yeah, so whatever you're doing to wrap Claude is broken. Because it's breaking the UI. "It's never bothered me". Cool. But your tool is bugged.

kstenerud 5mo ago
Feel free to open a bug report if it bothers you. Or a PR. Or feel free to avoid the tool entirely if this UI issue shakes your faith in its overall quality down to its very foundations. This is hardly a hill to die on.
- sjagauanbdvva 5mo ago
  You’re missing the point. You claimed high quality and provided a repo. Did you not expect someone to actually look and critique it? Whether the visual bugs are a deal breaker or not isn’t the point. The point is that’s not high quality code, it may work. But it’s not code I would ship at my job and therefore it’s not high enough quality for anyone serious
  - kstenerud 5mo ago
    Hey that's fine. You're free to make whatever judgment you wish. But I still stand by the quality of my code, including here. You and I don't need to agree. What decades of managing codebases (public and private, huge and small) has taught me is that there will always be an endless list of bugs and feature ideas and nice-to-haves and technical debt pressures in any given project. You'll never get to them all, so you prioritize (as I have done here). Functional bugs usually trump visual ones unless they're actually interfering with work. Will I fix this bug? Probably, now that I'm aware of it. But there are more important matters to attend to first. Edit: Turns out the bug comes from a mismatch with the terminal I'm using. With other terminals it looks fine. Term caps are surprisingly complicated, especially when you have multiple layers!
    - hiw2d 5mo ago
      tbh youve embarrassed yourself here.
      - kstenerud 5mo ago
        THAT must be why the stars are going up! Thanks for explaining it for me.
        gilrain 5mo ago
        And as we know, GitHub Stars are the same as truth. Very persuasive.
        godelski 5mo ago
        Sorry dude, 84 stars isn't that much. It's a good number, be proud, but I wouldn't go boasting about it like you're some hotshot. https://www.star-history.com/?repos=kstenerud%2Fyoloai&type=date&legend=top-left https://www.star-history.com/?repos=kstenerud%2Fyoloai&type=...
    - gilrain 5mo ago
      > But I still stand by the quality of my code, including here. You and I don't need to agree. You aren’t having a disagreement with a person. You’re having a disagreement with reality.
      - kstenerud 5mo ago
        > You aren’t having a disagreement with a person. You’re having a disagreement with reality. How so? Are you going to instruct us all on how a termcaps mismatch bug is an indicator of poor code quality, rather than an unfortunate bug emerging from within the chaos of the many layers of disparate technologies that must somehow be stitched together (along with their idiosyncrasies) in order to make a project like this work?
        sjagauanbdvva 5mo ago

kstenerud 5mo ago

Feel free to open a bug report if it bothers you. Or a PR. Or feel free to avoid the tool entirely if this UI issue shakes your faith in its overall quality down to its very foundations. This is hardly a hill to die on.

sjagauanbdvva 5mo ago
You’re missing the point. You claimed high quality and provided a repo. Did you not expect someone to actually look and critique it? Whether the visual bugs are a deal breaker or not isn’t the point. The point is that’s not high quality code, it may work. But it’s not code I would ship at my job and therefore it’s not high enough quality for anyone serious
- kstenerud 5mo ago
  Hey that's fine. You're free to make whatever judgment you wish. But I still stand by the quality of my code, including here. You and I don't need to agree. What decades of managing codebases (public and private, huge and small) has taught me is that there will always be an endless list of bugs and feature ideas and nice-to-haves and technical debt pressures in any given project. You'll never get to them all, so you prioritize (as I have done here). Functional bugs usually trump visual ones unless they're actually interfering with work. Will I fix this bug? Probably, now that I'm aware of it. But there are more important matters to attend to first. Edit: Turns out the bug comes from a mismatch with the terminal I'm using. With other terminals it looks fine. Term caps are surprisingly complicated, especially when you have multiple layers!
  - hiw2d 5mo ago
    tbh youve embarrassed yourself here.
    - kstenerud 5mo ago
      THAT must be why the stars are going up! Thanks for explaining it for me.
      - gilrain 5mo ago
        And as we know, GitHub Stars are the same as truth. Very persuasive.
      - godelski 5mo ago
        Sorry dude, 84 stars isn't that much. It's a good number, be proud, but I wouldn't go boasting about it like you're some hotshot. https://www.star-history.com/?repos=kstenerud%2Fyoloai&type=date&legend=top-left https://www.star-history.com/?repos=kstenerud%2Fyoloai&type=...
  - gilrain 5mo ago
    > But I still stand by the quality of my code, including here. You and I don't need to agree. You aren’t having a disagreement with a person. You’re having a disagreement with reality.
    - kstenerud 5mo ago
      > You aren’t having a disagreement with a person. You’re having a disagreement with reality. How so? Are you going to instruct us all on how a termcaps mismatch bug is an indicator of poor code quality, rather than an unfortunate bug emerging from within the chaos of the many layers of disparate technologies that must somehow be stitched together (along with their idiosyncrasies) in order to make a project like this work?
      - sjagauanbdvva 5mo ago