made you look
It’s unclear why Google stuck with PNG for HDR screenshots instead of a format supported by Ultra HDR such as JPEG.
Because for good lossless HDR you’ve got a grand total of 2 options, PNG and JPEG XL. And Google don’t want people to know of yet another use case for JXL.
NTFS was designed back in the mid 90s, when the plan was to have the single NT kernel with different subsystems on top of it, some of those layers (i.e. POSIX) needed case sensitivity while others (Win32 and OS/2) didn’t.
It only looks odd because the sole remaining subsystem in use (Win32) barely makes use of any of the kernel features, like they’re only just now enabling long file paths.
Qt is overkill if all you’re using it for is to create a window you render into, something like SDL would be better.
Jack Dorsey may have had lofty goals for Bluesky, but he doesn’t even work there anymore.
Which is a point in Bluesky’s favour.
You can’t do normal BitTorrent in browsers, there’s no support for plain sockets that you’d need to communicate with other peers, WebTorrent is technically a new protocol that implements the BT semantics over stuff the browsers do provide (So you can proxy between the different swarms, that’s the “hybrid” nodes in the image on the WebTorrent page)
But it turns out it’s all a moot point, since PeerTube removed WebTorrent support anyway in favour of their own P2P system
Edit: Ok so I misunderstood, and it seems like it’s a bit complicated. The server can (it’s disabled by default) use WebTorrent to import videos, the client still uses the WT trackers to find peers but uses a different protocol to actually share the video data.
There’s this tool that provides the ability to automatically seed videos, but development has stalled because no up to date client will ever make use of it.
I think the one remaining use is the “download as torrent” option, but even then that’s just using a web seed, so it’s just an alternative way to download the video.
Unfortunately WebTorrent isn’t compatible with normal BitTorrent, so unless you’re using a client that specifically supports it, you’re not helping out any PeerTube clients
His personal LLC is called “Excession”, considering some of the plot points in that book I doubt he enjoyed it at all, it’s just “nerd set dressing”.
At the time it was just an ad-lib by Jason Issacs, guessing he wished on a monkey’s paw for it to make sense in context.
What’s the problem with that, though? Systems like that are pretty much guaranteed to be isolated from the internet.
Because things break down eventually, and when it comes time to buy replacement parts you discover that they’re effectively impossible to find. Then instead of having a nice, planned transition period you’ve got like a weekend to cobble together something to get it working again.
although I’m not sure what USB4 Gen 3×1 is, but it’s only x1 so can’t be that good, right?
It’s the initialisation mode of USB 40Gbps, luckily not something users will have to deal with
They really want to promote their AVIF format, and supporting JXL would hinder that (Since JXL is a much nicer upgrade path from JPEG/PNG than AVIF is)
Like you can transparently go from JPEG to JXL and back with no loss, which isn’t possible with AVIF. And PNG to JXL gives you a smaller file, while it’s usually the opposite with AVIF (Unless you get lucky, as lossless AVIF can be beaten by a BMP in a ZIP file). There’s also the issue of speed, AVIF is slow to encode compared to other formats (And while hardware decoding is possible, it’s also geared towards video, so the quality is often lacking, and can sometimes be slower than plain software encoding)