So I just read over at the Laravel News that Github has introduced reactions. The code-sharing, version-control, platform har added reactions to issues and pull-requests, where a lot most the discussions take place. Part of why Github has elected to add reactions is in part due to the “open-letter” by the community, and they wanted to address the problem that many people in fact “react” to issues, pr’s and so on with emoji. This creates a lot of clutter and noise, as the discussion thread is full av emoji and no content. Secondly they also wanted to let people express their feelings more effectively.
We’re adding Reactions to conversations today to help people express their feelings more simply and effectively. – Github
And sure, I get all this and it is a good move indeed. However, you saw that coming didn’t you 😉
However, the “reactions” they have chosen. I do really wonder if they’ve done as much research as Facebook did for which emoji, or reactions, they have chosen. Facebook wrote a long post on how, what and why they chose the ones they did. How did Github and up with thump up/down – laugh – confused – heart – hooray?
On the Github blog they do say that:
”We decided to choose reactions that are relevant to the conversations people have on GitHub. cover the range of reactions our users typically express through comments on GitHub. We’re looking forward to seeing how the GitHub community uses this set of reactions.”
But who says “hooray” for example, really?
And then there is the timing, are they really reacting to the “open-letter” or just copying Facebook.
Oh well, my ramblings, I do like the feature though – nice one octocats!
What’s your take on Github reactions?
Great post! Thanks for the information shared with clarity. I have read your post, which is very helpful, if someone wants to know more about shopify development services