#mng

@ozamidas @caiocgo
This may be an unfounded accusation, but the fact is that over time @mozilla has been progressively less supportive for the #indieWeb, #openWeb, and open standards. There are innumerable examples of this, but my pet peeves are: removal of native support for #RSS (and Atom) feeds, removal of the Live Bookmarks feature without an official extension to replace it, lack of support for #MNG, and now the reticence in making #JPEGXL support official.
2/

マイニューギア...　#mng

The only browser I actually know of that _can_ support #JpegXL is #OtterBrowser https://otter-browser.org/ —a basically one-man effort to wrap the classic Opera/Presto UX on top of Qt-based web engines— and even then under the very specific conditions that the QtWebKit engine is used, with an environment variable set to enable support for “unsafe” formats (this, BTW, enables support for #MNG too).

I should clarify that I'm not claiming that their “other” products are useless, or that we would be better without, but rather that the #openWeb, and in fact #FLOSS in general, would benefit more if they invested more in their main product(s) rather than claiming “lack of resources” for their choices to not give standards the support they deserve.
And yes, this is (also) about my pet peeves (#RSS, #MNG, #JPEGXL, dropped and newer protocol support), but it goes beyond that:

#MNG
#lumixg9pro

#mng

Again, this isn't about #MNG or #JpegXL or #RSS or web feeds support _specifically_: it's about the priority policies.

I do understand and appreciate that even just the maintenance of the engine to keep the pace with the evolution of the web standards is a huge undertaking —it's why so many browsers have just given up and chosen to “leech” on WebKit or Blink instead.

When the only reason to use your browser is that it's the only FLOSS alternative to Google's, you have a problem.

Two of my #petPeeves in this regard are with #Mozilla #Firefox, and in both cases they are about feature removal because of perceived bloat.

The first is the removal for the support of the #MNG format. The purported reason for this was the “bloat” coming from linking a 200KB library. Reading the issue tracker for this, 20 years later when Firefox installations are 200MB and counting is … enlightening:
https://bugzilla.mozilla.org/show_bug.cgi?id=18574

#MNG 宣言してなかったけど
こっそりIYHしてました

#mng

何か届いた！ #MNG

#MNG

#MNG