I don’t know how it started, but sometime after WordPress switched to Slack in 2014 the norms for checking in to a dev chat switched to emoji. Many people , some use slack specific emoji like the bowtie, and others change it up on a regular basis.
Like many traditions, this started completely organically and at this point it’s so normal, no one bats an .
I feel like It’s important to have traditions in open source software, but it’s also important to make them easy to pick up. It helps new contributors feel a part of the process. If the traditions are too hard to pick up on, then you risk creating an us vs. them problem. Thankfully, emoji’s to show you are present is one that people can pick up on right away and immediately feel a part of the WordPress team.
WordPress 4.2 is almost here. Yesterday marked the release of Beta 4 and if everything goes as planned, the first RC will be available next week. One of the
“features” that people are talking about in both positive and negative terms in emoji support. I put feature in quotation marks because really, emoji support is a bug fix.
Some browsers don’t know how to render emoji , or they have bugs in their implementation . Notably, Chrome either doesn’t work or has bugs, older versions of IE don’t work, and Firefox has bugs.
Not all sites will be able to upgrade to utf8mb4, which means they’ll be unable to save emoji characters that they enter.
Not being able to use emoji makes everyone a sad panda (), so we need to fix this.
Fixing WordPress to work in more languages exposes emoji. Since emoji support isn’t great yet, WordPress needs to shim it. Most users won’t understand why their site works in some browsers but not others. Some people find emoji annoying. Others find them fun. But as of WordPress 4.2, we all can at least find them.