9 | | Yes. |
10 | | |
11 | | **''Single mime approach VS multiple mimes approach''**. |
12 | | |
13 | | I think this depends on 2 things. |
14 | | |
15 | | 1. How much are we willing to wait for having this "feature" in wordpress? |
16 | | |
17 | | If multiple mimes type support is not included now, it will take us at least another 5 years to add it. |
18 | | 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. |
19 | | This is unfortunate truth of wordpress's current situation. |
20 | | 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. |
21 | | 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. |
22 | | Even if you do so, you need to wait for another year to make it prove that it is "battle-tested". |
23 | | 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. |
24 | | 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. |
25 | | This is just a waste of time. |
26 | | |
27 | | 2. Whether are you willing to add multiple mimes support now and then slowly improve wordpress's legacy code associated with it? |
28 | | There is nothing like "larger re-imagining/refactoring". Things are improved slowly over time. |
29 | | |
30 | | **To sum this up, if you are willing to improve media handling of wordpress, then take multiple mimes approach. |
31 | | If you don't time for it, then take Single mime approach.** |