3 ms·
I'm confused. How would this solve the problem? Whilst looking different is clearly an issue (e.g. the gun being depicted a water gun), I'm not sure what your s
by 2T1Qka0rEiPr 7y ago
I'm confused. How would this solve the problem? Whilst looking different is clearly an issue (e.g. the gun being depicted a water gun), I'm not sure what your solution would look like? Images hosted somewhere? You'd get consistency, but you'd lose universality. It goes without saying, but you can use Emoji practically _anywhere_ that support text. That's huge.
- jfk13 7y agoAlthough it depends on having the same level of emoji support across all the relevant systems/devices. If you send a message with Unicode 13 emoji to me and I read it on my phone that's stuck on Unicode 10, it's not much use. Whereas if these silly little images were represented by links to a canonical repository somewhere, newly-added images could automatically work even in pre-existing systems. On the other hand, that'd be dependent on connectivity.
- 2T1Qka0rEiPr 7y agoYeh, so the current system seems better, because, although it's versioned, it doesn't need to constantly communicate with some central server. Also, another drawback is fonts need to be updated, but again, I think the benefits outweigh the costs.
- joveian 7y agoArguably it might be better to include a limited, space-optimized vector image format (something like HVIF, Haiku Vector Icon Format[0]) along with text rather than try to enumerate emoji, although there are also advantages to the current approach (smaller size for supported characters and meaning indpendent of representation). For the web there is already data: url and similar inline image options would be possible in many situations even without the basic text format including images. [0] https://blog.leahhanson.us/post/recursecenter2016/haiku_icons.html https://blog.leahhanson.us/post/recursecenter2016/haiku_icon...