

If I’m going to be totally honest: implementing anything in #curl is about fourteen times easier and more fun than the thread- and object-spaghetti that is #Firefox code… But don’t tell anyone I said this.
I write curl. I don’t know anything.


If I’m going to be totally honest: implementing anything in #curl is about fourteen times easier and more fun than the thread- and object-spaghetti that is #Firefox code… But don’t tell anyone I said this.


After I wrote (most of) the DoH implementation for #Firefox it was not too hard to subsequently add support for DoH in #curl.


@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…


@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


@leeloo@techhub.social they are indeed quite different beasts in the insides. #curl is not C++ spaghetti using a million threads for example. 😁
@sampe@piipitin.fi thanks!