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

  • moxOP
    link
    52 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
      link
      fedilink
      English
      152 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@feddit.uk
        link
        fedilink
        102 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
          link
          fedilink
          English
          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@feddit.uk
            link
            fedilink
            4
            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

      • 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.

    • @some_guy
      link
      32 months ago

      Exactly. The complaint is that a basic feature no longer works as expected.