this post was submitted on 23 Jul 2024
92 points (78.8% liked)

Programming

17668 readers
174 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] eager_eagle@lemmy.world 15 points 5 months ago (2 children)

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 10 points 5 months ago (1 children)

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 5 points 5 months ago* (last edited 5 months ago) (1 children)

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 4 points 5 months ago* (last edited 5 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.