Not my blog, but the author’s experience reminded me of my own frustrations with Microsoft GitHub.

  • mox@lemmy.sdf.orgOP
    link
    fedilink
    arrow-up
    8
    arrow-down
    3
    ·
    2 months ago

    From what I gather they’re salty that GitHub is switching to react?

    No, that is not the point at all. React is just an incidental detail she considered while trying to figure out what was going on.

    • Eager Eagle@lemmy.world
      link
      fedilink
      English
      arrow-up
      18
      arrow-down
      3
      ·
      2 months ago

      It’s not an incidental detail when the text is almost entirely around the issue caused by this (mis-)use of react. The author doesn’t give another argument to support their view.

      • Rogue
        link
        fedilink
        arrow-up
        10
        ·
        2 months ago

        There seems to be a rando paragraph about AI as well,then it trails off that they’re looking for recommendations for git blame clients. I couldn’t really figure out how it was all GitHub’s fault or where the word legacy fits in.

        • Eager Eagle@lemmy.world
          link
          fedilink
          English
          arrow-up
          5
          ·
          edit-2
          2 months ago

          The thing is a new feature - AI-related in this case - contradicts the idea of legacy software to me, so I really don’t know what was the point of that other than “complaining about github”.

          • Rogue
            link
            fedilink
            arrow-up
            5
            arrow-down
            1
            ·
            edit-2
            2 months ago

            OP also felt the need to refer to the platform as Microsoft GitHub. So it seems likely this is all just grumbling about evil corp making changes

      • zygo_histo_morpheus@programming.dev
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        There’s a difference between the author being mad that github is switching to react and the author being mad that github is misusing react. It is possible to use react without breaking browsers find in page functionality, which is ultimately what the author is frustrated about.