bagder

joined 7 years ago
sorted by: new top controversial old
#Firefox joins the other browsers and disables HTTP/2 server push. in c/[email protected]
[–] [email protected] 1 points 1 month ago (1 children)

@[email protected] 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.

#Firefox joins the other browsers and disables HTTP/2 server push. in c/[email protected]
[–] [email protected] 1 points 1 month ago

@[email protected] right, presumably not widely used but we can't really tell...

2
#Firefox joins the other browsers and disables HTTP/2 server push. (mastodon.social)
 

#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

The current JPEG XL decoder in #Firefox apparently consists more than 100,000 lines of multi-threaded C++ in c/[email protected]
[–] [email protected] 0 points 2 months ago (1 children)

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

The current JPEG XL decoder in #Firefox apparently consists more than 100,000 lines of multi-threaded C++ in c/[email protected]
[–] [email protected] 0 points 2 months ago (4 children)

@freddy ... and that happens to be the one Firefox uses...

The current JPEG XL decoder in #Firefox apparently consists more than 100,000 lines of multi-threaded C++ in c/[email protected]
[–] [email protected] 1 points 2 months ago (3 children)

@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

4
The current JPEG XL decoder in #Firefox apparently consists more than 100,000 lines of multi-threaded C++ (mastodon.social)
 

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

I promise, just because #curl and #Firefox often behave similarly, it is almost never because I once worked in the Firefox networking team. 🤠 in c/[email protected]
[–] [email protected] 2 points 2 months ago (1 children)

@[email protected] they are indeed quite different beasts in the insides. #curl is not C++ spaghetti using a million threads for example. 😁

I promise, just because #curl and #Firefox often behave similarly, it is almost never because I once worked in the Firefox networking team. 🤠 in c/[email protected]
[–] [email protected] 1 points 2 months ago

@[email protected] I feel I have at least two!

3
I promise, just because #curl and #Firefox often behave similarly, it is almost never because I once worked in the Firefox networking team. 🤠 (mastodon.social)
 

I promise, just because #curl and #Firefox often behave similarly, it is almost never because I once worked in the Firefox networking team. 🤠