If you look at the code, it's because for whatever reason, the emoji loader code creates an array that maps tags to emojis... but for some reason, they decided to implement this by storing an array of tags and then binary searching that array for EVERY TAG that must be updated -- consider that each of the 5,000 some emojis have multiple tags! Plus, they create multiple DOM elements for each emoji! This code has O(m * n * log(n)) complexity, where m is the average number of tags per emoji and n is the number of emojis. This code could very simply be sped up by using a hashmap (which is builtin with JS's Map) or by doing this work on the server and saving the result, so you would send back a JSON file like
{
"tags": {
"marsey": ["marseylove", "marseyfemboy", ...],
"othertag": ["emoji1", "emoji2"....]
}
}
Jump in the discussion.
No email address required.
Instead of the dom nodes just use class with background image on the pseudo element in a minified style file that is async. You could frick with turning them into inline svgs but with so many files your css file might explode in size, but it is handy for common shit. Be sure to cache all these files too or you're really ducking yourself
That will be $1500 dollars pay whenever
Jump in the discussion.
No email address required.
More options
Context