[wp-trac] [WordPress Trac] #55443: Create WebP sub-sizes and use for output

[WordPress Trac]

#55443: Create WebP sub-sizes and use for output
-------------------------------------------------+-------------------------
 Reporter:  adamsilverstein                      |       Owner:
                                                 |  adamsilverstein
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.1
Component:  Media                                |     Version:  6.0
 Severity:  normal                               |  Resolution:
 Keywords:  has-unit-tests needs-dev-note        |     Focuses:
  needs-docs needs-user-docs needs-patch 2nd-    |  performance
  opinion needs-testing changes-requested        |
-------------------------------------------------+-------------------------

Comment (by snoringdragon):

 Hi, there.

 > I agree with your suggestion of only generating WebP format images.
 Also, I like the possibility of having a (filterable) “threshold” value
 above which (only) JPEGs are generated.

 This is a great measure.

 > One advantage of retaining some sizes is we can also use these JPEGs as
 fallback images for the edge cases where WebP still isn’t supported (eg.
 Open Graph tags).

 Yes.

 **''Single mime approach VS multiple mimes approach''**.

 I think this depends on 2 things.

 1. How much are we willing to wait for having this "feature" in wordpress?

 If multiple mimes type support is not included now, it will take us at
 least another 5 years to add it.
 It has nothing to do AVIF support but more about wordpress
 users/committer's tendency to not improve wordpress unless there is no
 more chance to shelve it further.
 This is unfortunate truth of wordpress's current situation.
 Let's say someone courageous enough decided to have this added after 2 or
 3 years, someone will surely pop to say that this should be done as a part
 of bigger refactor.
 Even if you refactor whole thing, someone will pop to say that such big
 refactor should not be made into wordpress as it is not "battle-tested" so
 let's make it into feature plugin first or they may say that this multi
 mime support should be made into a feature plugin first.
 Even if you do so, you need to wait for another year to make it prove that
 it is "battle-tested".
 Even if it is "battle-tested", someone may say that feature plugin did not
 have a lot of installs so it is still not ready or it has not "aged"
 enough.
 Even if it has good installs, someone may say that it is still not needed
 as AVIF still does not have full support or there is better technology out
 there so let's wait for that tech to mature.
 This is just a waste of time.

 2. Whether are you willing to add multiple mimes support now and then
 slowly improve wordpress's legacy code associated with it?
 There is nothing like "larger re-imagining/refactoring". Things are
 improved slowly over time.

 **To sum this up, if you are willing to improve media handling of
 wordpress, then take multiple mimes approach.
 If you don't time for it, then take Single mime approach.**

 Hope that it helps.
 Thanks.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/55443#comment:134>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform