@lukasa@hachyderm.io in curl's case we only offer it via an API but that also means we cannot very easily take it away without risking hurting a few users... Ie we would need to bump SONAME.
@icing@chaos.social right, presumably not widely used but we can't really tell...
#Firefox joins the other browsers and disables HTTP/2 server push.
libcurl still supports it!
<https://groups.google.com/a/mozilla.org/g/dev-platform/c/vU9hJg343U8/m/4cZsHz7TAQAJ?pli=1>
@freddy you're reading too much into my words. I'm just amazed by how large the existing JPEG XL decoder is.
And I don't think I am alone.
@freddy ... and that happens to be the one Firefox uses...
@Di4na possibly: I believe Rust is generally a good thing for most things, but I believe the Rust ecosystem with cargo and bazillions of always-updatiing tiny dependencies risk adding friction and at least complicates the equation quite a lot
The current JPEG XL decoder in #Firefox apparently consists more than 100,000 lines of multi-threaded C++
For just decoding an image format.
Not sure what it says about the format, the implementation and the Internet at large.
<https://github.com/mozilla/standards-positions/pull/1064>
@leeloo@techhub.social they are indeed quite different beasts in the insides. #curl is not C++ spaghetti using a million threads for example. 😁
@icing@chaos.social I feel I have at least two!
I promise, just because #curl and #Firefox often behave similarly, it is almost never because I once worked in the Firefox networking team. 🤠
daniel:// stenberg:// @mastodon.social Internet protocols geek at wolfSSL. I lead the curl project. I don't know anything.