• To be frank this decision to include emoji support in core is a bad one. never to my knowledge has wordpress automatically injected additional css and js into the DOM to support something that seems trivial and quite frankly OPTIONAL. This sets a bad precedent for future wordpress releases. what is to stop wordpress from injecting other assets into the DOM that we just dont want loaded? yes you can disable them, but shouldnt it be in reverse? shouldnt you ENABLE them? this is by definition feature bloat (https://en.wikipedia.org/wiki/Software_bloat) and core decision makers should be cautious of preceding down this road or they may find themselves without the core following they currently have.

Viewing 5 replies - 1 through 5 (of 5 total)
  • It is horrible indeed, why add that stupid bloat to 20% of the internet? If I want emojis I either create or install a plugin.

    The only and most horrible decision by WP.

    Moderator cubecolour

    (@numeeja)

    You can use a lightweight plugin to remove the emoji code:
    https://www.ads-software.com/plugins/disable-emojis/

    This is an appalling decision by core to include Emoji’s by default. The Emoji scripts js files make up 12% of files served on our server.

    Frankly emoji inclusion in core is one in many unusual decisions by core. I’ve been told it’s because WordPress core is now being written to suit WordPress.com and no one else.

    Cases like the emoji issue would suggest this is true.

    Alec Kinnear

    PS. I can’t believe I have to add a plugin to disable what should be at worst just a Reading or Writing option checkbox (and that across dozens of sites).

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    This topic really has been done to death and I think the best summary can be found at this link.

    https://www.ads-software.com/support/topic/get-rid-of-emoji?replies=30#post-6872992

    There’s not a lot of value to constantly revisit decisions that were made months ago. This isn’t a conspiracy, it’s not “arrogance” nor is it “WordPress core developers hates and ignores it’s users!”

    That last one is my personal favorite. Seriously, I can’t get enough of that vitriol and downright toxicity.

    The decision for the core team to implement features comes from the honest question of “Does this meet the needs of the majority of users?” While there is a strong current of emphatic and upset users, that repetitive disagreement does not necessarily represent the majority.

    *Re-reads what I just typed*

    I get it, I really do. Some places in the world ban the emoji URLs and some people don’t want any additional code on their site.

    But like most things in WordPress with a few lines of code or a plugin (a plugin is the optimal way to go for users who have a problem).

    If you do want to use a plugin try one of these.

    https://www.ads-software.com/plugins/disable-emojis/

    If you want to disable the emojis and also revert all the smilies to the original ones, this will do it:

    https://www.ads-software.com/plugins/classic-smilies/

    If you want to code your installation yourself, then please look at the source for “Disable Emojis”.

    https://plugins.trac.www.ads-software.com/browser/disable-emojis/trunk/disable-emojis.php

    It’s not a lot of remove_action() and remove_filer() and the code is very simple.

    I’m closing this topic now. If another moderator feels like re-opening it then I am fine with that. But this topic has really been done and contributing to the core development isn’t this. Please follow make/core for good examples of how to contribute.

    https://make.www.ads-software.com/core/

    Andrew Nevins

    (@anevins)

    WCLDN 2018 Contributor | Volunteer support

    Opening to add a little link and then running away: https://www.ads-software.com/about/philosophy/

    It always helps me figure out why when ever a feature is added or removed.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Emojis In WordPress – injecting css and javascript’ is closed to new replies.