It's certainly a hit in the West, though. Every social media outlet I see is flooded with various emoji. Clearly people are using them, and Unicode has plenty of space, so why not standardize? If anything, it will slow down the proliferation of emoji.
We could just create a WingDings-esque font for containing all of this stuff. It would be better to incorporate multi-font support into more devices rather than incorporate informal symbols into Unicode.
I am aware of the massive number of symbols represented in Unicode, but it seems that the vast majority of them are related to existing languages, or other symbols that are used in government. Not 400 different smileys of every race, and cats...
Edit: By creativity, I mean that Unicode is about expressing language and officially-recognized symbols. Incorporating art into it is contrary to the purpose of Unicode.
Some of the dead languages in Unicode arguably were never "real" languages and history disputes if they were actual written forms for a language or merely local doodles. Their relevance to Unicode is apparently there is so much academic work still trying to sort out said history that papers are written all the time with those dead symbols. (For all we know, some of them may even be ancient emoji. :P )
The difference between "formal" and "informal" is a fuzzy zone. It's almost like we're making up all of language as we go along. Unicode seems like a fine place to standardize our growing need for emoji. Also, for what it is worth, all of WingDings is also in Unicode and has been since early on.
My only criticism with emoji in Unicode is that I do think it means that Unicode should reconsider its stance on previously closed proposals for constructed languages like Klingon and Tengwar and maybe dedicate a section somewhere outside of the basic multilingual plane (BMP) for them.
If you think emoji is an expressive language, then I'd like you to make an argument toward that point in emoji.
1. Emoji only typically exists in the written form, but that isn't really a strike against it: paragraphs, capital letters, and (to some extent) word-breaks only exist in the written form too.
2. They have a conceptual existence, and communicative force, that is separate from any particular representation. You can't copy-write the smiley grapheme. You could copy-write a particular smiley image (or "graph"), much like you could copy-write a glyph, but that's it.
Finally emoji is important for many young children in Japan and China, (I'm not an expert on this). The issue is learning all the characters needed to express yourself is pretty hard and takes years longer than learning the latin alphabet. Further learning how to input characters on a computer takes even longer. However kids still want to communicate with each other and as a result use a lot of emoji to speed up the process for them. For them emjoi is how they want to express themselves.
The problems with a specific font for extra characters are: who would standardize it? And (assuming Unicode) how would they be represented in code points? You could use Unicode's Private Use Areas,[0] but from my understanding that might result in different characters viewed for the recipient if their implementation overlaps yours.
(Well, that, and asserting a minimum shared base of symbols that each WingDings font is expected to have depictions for. I think that's a less important role, though; they could just as easily get away with shipping a "Unicode-official fallback emoji font" instead, that would backfill for any codepoints a particular OS's emoji font doesn't have.)
---
† Identifiers for the pictures themselves, not the concepts they represent. That's an important distinction, I think: there really isn't a difference in concept between U+1F601 'GRINNING FACE WITH SMILING EYES' and U+1F638 'GRINNING CAT FACE WITH SMILING EYES'—but they're different little pictures. Effectively, they're like an icon/logotype/mark, with each font giving you a different artist's treatment on that mark.)
And what are dingbat typefaces if not emoji under an other name? Nobody cared when unicode added U+2701 UPPER BLADE SCISSORS and U+273B TEARDROP SPOKED ASTERISK.
The debate isn't about how to standardize the display of symbols on platforms, but how to allow the incorporation those symbols into everyday text.
Are you confused? U+2701 UPPER BLADE SCISSORS is a Unicode codepoint, it can most definitely be used "within regular text of another typeface".
> given the limited scope of dingbats symbols
There is no limited scope, dingbats is just stuff that's neither numbers nor "letters".
Just because nobody complained doesn't mean that it wasn't a problem.
A polluted standard makes it more difficult to implement the standard. In practice this is passed on to the user in performance and monetary cost, not in something more visible. The fact that you don't understand the problem is due to you not working with Unicode at a low level.
The amount of mind reading you believed you managed to accomplish from a setup and a punch line is pretty astounding. Maybe leave that to the magicians?