Using the Disable Emojis plugin removes the new emoji functionality in WordPress 4.2. WordPress does not need emoji. Probably, the worst decision ever made by WordPress Core is enabling emojis by default, and providing no way to disable them. WordPress core developers should have a disable setting instead of having to install another plugin. Emoji functions add 5.6k to 14.7k page weight and 2 or 3 HTTP requests to a site.
Emoji are the square-grid ideograms, emoticons, or smileys used in Japanese electronic messages and Web pages, the use of which has spread outside Japan. Originally meaning pictograph, the word emoji literally means “picture” + “character.”
Beyond the standard emoticon-type “smileys,” there are hundreds of emoji, ranging from plants and animals to people, objects, vehicles, food, the Sun and Moon, and more.
We think emojis are a waste of bandwidth.
As of July 2016, disable Emojis plugin has over 30,000 active installs.
As of January 2017, disable Emojis plugin has over 50,000 active installs.
Note about why Emojis happened:
You know emojis in itself are just great, but they should never have been implemented into CORE. Why? At least 98% of active WP sites simply do not use them, still it occupies space and some milliseconds will be wasted in vain. That is a trade-off for nothing for the majority. That is why emojis should have been left as a plugin.
FYI, The emoji implementation was also a way to quietly patch a massive security vulnerability.
Andrew Nacin walks step by step through how a critical security vulnerability was discovered in WordPress core code and then patched using emoji as a trojan horse in WordPress 4.2.