a-french-anon

> but I do have what can be said to be an irrational preference for JXL.

Is it irrational to follow the collective "one format to rule them all" dream? Sure, the codec itself needs work, but seeing how long we've been stuck with the JPEG/PNG/GIF trio (even with better encoders like mozjpeg/jpegli or optipng/zopfli) with TIFF as a catch-all backup, getting the format right once and for all really matters.

I'm still weirded by the low amount of workforce in libjxl/jxl-rs; sure, too many cooks do ruin the broth, but too few too, in that domain.

sixel works "fine" though.

Me too.

"Hmmm-mmm, I smell pork chops. Does your dad cook?"

Pretty sure that you can use DHCP and still override the DNS servers with most DHCP clients.

Just a PSA for people who don't know and have a "normal" DPI monitor: bitmap fonts are intentionally not supported by Kitty.

Trying to repost it (https://news.ycombinator.com/item?id=50245592) to see if it gets a bit more attention. Really thorough benchmarking and improvements, promising gains in other areas of ECL too.

You don't read Lisp via the parentheses, but via the indentation. It's almost like Python but the (s and )s are for the computer to see.

Tip from a Frenchman: Camembert is an overglorified version of Brie. The one you need to see is where the "king of cheese" is made: Roquefort-sur-Soulzon.

I think it's saner to be literal here. Reference counting is a way to automatically collect garbage for you. Why shouldn't it be called a GC then?

Electric Miata when?

This doesn't look like it has wired support?

Do you just want to use "sets of haplogroups with similar phenotype" instead? I mean, you can argue all day that the existence of the orange color somehow means that there's no difference between yellow and red, but you're just going to look foolish.

Which is kinda ironic because Toyota is probably the only one that did hybrid from the ground up with their HSD transmission.

For decoding, yes, dav1d. But for encoding, a lot more SIMD kernels in libaom/SVT-AV1 written by other people.

(And lots of kernel shared between decoding and encoding, of course)

The third for me is that LLM usage has exploded for the development of core Julia itself (just look at the PRs).

Yes, but for speed which means a lot of SIMD plumbing, the larger workforce certainly benefited AV1 codecs!

Sorry for the dumb question, but I don't understand something in these graphs. Since it's x=speed and y=bd-r, is this test done at a fixed target quality/size?

What do you think about the fact that most perceptual quality improvements in SVT-AV1 have been almost only driven by external, non-paid enthusiasts such as yourself while the maintainers have been basically only targeting VoD and RTC?

Compared to JXL (which admittedly has almost nobody working on except veluca these days...) which was focused on it since the beginning, I think it really matters.

Wait... SVT-AV1 doesn't support anything else than 4:2:0, right? Kinda biases the comparison here.

Bubblewrap is a CLI interface for these, you know? It's been some time since bwrap recommended avoiding their SUID wrapper.

Same except for Steam. Hope this money revitalizes bubblewrap's development, it'd be nice to get proper signal handling cleanup up then merged (even util-linux's unshare has it, these days).

I wasn't when I saw they made the exact same stupid error as Python: if and switch are statements, so that you need a stupid ternary operator to do the same.

You seem to be ignoring that most people who want off the infernal npm/cargo hamster wheel are conscious that it implies a bit of spoilt milk or moldy bread in exchange for stability and that they're fine with it.

The gains are just too numerous and important to reject the few rust spots on a "good enough" stdlib.

But well, the kind of people who nod a bit too much while reading https://boringtechnology.club/ aren't using Rust. They're on C99, ANSI CL, Ada, maybe Python, Perl or Tcl.

> You can video-conference while pooping without touching a switch

｢ ＴＨＥ ＦＵＴＵＲＥ ｣

Please, for your own sake and that of your ideals, don't fall into a Disney adult mentality of "these are bad guys who are clearly against Truth and Good^tm!" just because righteousness feels good. This falls under underestimating your enemy and never serves the people embracing said feeling.

Well, not that important to me since we already had that in Vapoursynth.

I find it very easy to solve some of these physics questions by thinking about a degenerate version of it instead, with exaggerated parameters (since these physics phenomenons are described by continuous/monotonic functions).

So for the bowling ball, I replace it with an imaginary marble weighing 1 ton and the answer is now self-evident.

This article's comment section made me discover the hilarious "No crying in the casino" meme words, thanks.

Keyword: linked. Who would have thought that people with happy and fulfilling lives have something else to do than being online?

That guy is stupid, the part of human nature containing dishonesty also houses "following the path of least resistance", which means that these people will simply contribute to another leading compiler without these rules.

So the real question is: what's LLVM policy?