The_Decryptor

Pretty sure that’s just high-frequency trading.

Landrun as well, takes the restrictions on the command line. Can look messy, but does make it entirely standalone, so you can e.g. drop it into a service file as the readme shows easily enough.

Webp is a smaller file size than jpeg for the same image quality in almost all circumstances

For lower quality images sure, for high quality ones JPEG will beat it (WebP, being an old video format, only supports a quarter of the colour resolution than JPEG does, etc.) JPEG is actually so good that it still comes out ahead in a bunch of benchmarks, it’s just it’s now starting to show it’s age technology wise (like WebP, it’s limited to 8bpc in most cases)

It also doesn’t hurt that Google ranked sites using WebP/AVIF higher than ones that aren’t (via lighthouse).

Edit: I should clarify, this is the lossy mode. The lossless mode gives better compression than PNG, but is still limited to 8bpc, so can’t store high bit depth, or HDR images, like PNG can.

Edit 2: s/bpp/bpc/

Well, all websites are written in JS (on the frontend)

Not true anymore unfortunately, some sites are using frameworks compiled to WASM instead.

e.g. X is apparently using Yew now.

Edit: Ok the “apparently” is doing heavy lifting, since now I can’t find the original source I read about it. Turns out “X” is a garbage name with no searchability, only an idiot would use it.

Yeah, but that’s still not a lot of data, like LTR/RTL shouldn’t be varying within a given script so the values will be shared over an entire range of characters.

his company’s artificial intelligence products, as some of the most advanced scientific tools in history, will help the world solve climate change

Remember that joke about asking an AI to solve traffic, and when it responds with “Use trains” the user declares it must be broken?

“Stop burning fossil fuels and reduce emissions? That can’t be right!”

Valve uses SDL for their own games, so this stuff would have been worked on internally and developed alongside the hardware itself.

But that’s the benefit of open source in the end, when done well everybody wins. Valve gets to ensure that any game using SDL can function perfectly with their hardware (Deck, Controller and Frame), any devs using SDL in their games knows they get first-party hardware support, and gamers get the benefit of both.

At one point, years ago, they were talking about removing the screen resolution entirely, and just make it a copy of the window size values instead.

Guessing it broke too much stuff, since it seemed like a nice idea but never eventuated.

Windows doesn’t even have basic package management like every Unix-like OS does so you don’t have to individually update applications and go find them on the Internet

Funny thing is that it does (winget), but it’s a terminal app. Windows users who look down on Linux users for “needing” to use a terminal don’t want to bring it up, so Linux users also aren’t aware of it and never point to it as a counter example.

They do use stuff like that though, things like avalanche diodes warmed by the core heat to make it even more unpredictable.

But sometimes things don’t work the way they’re supposed to.

Þere must be a half dozen cheap ways to generate true random numbers.

The problem isn’t generating random data, it’s ensuring it’s “high quality” (It’s all statistical checks, you can’t know ahead of time what random numbers should look like, otherwise they’re not random)

That’s the problem the AMD chips seem to have, that function is failing and letting through low quality data it should otherwise reject.

Because it’s not about the files anymore, it’s the free space on the disk you care about (Or rather, the filesystem metadata describing it, the free-space bitmap in the case of exFAT)

If the files are highly fragmented and spread out, then the empty space around the files is also broken up and spread around, which makes it harder for a filesystem to efficiently store new stuff as it now has to break up and pack new file data into the gaps.

winget is actually smart enough to manage stuff installed outside of it, but that still requires users to actually use winget to begin with.

For all the wireless printers I’ve ever owned CUPS would recognize the printer once, do a job, and then magically act like the printer either doesn’t exist or is currently doing a job in perpetuity.

I mean odds are it’s the printer that’s acting up. I owned a brother laser printer that I had to connect via the network, and that thing only ever configured the network on boot. If anything happened to the network connection it’d go offline until you restarted it.

There’s a reason I’ve seen multiple people recommend using something like a Raspberry Pi connected via USB as a replacement print server rather than relying on the native printer support. And since the modern printer protocols are basically lifted from CUPS, compatibility would be improved.

The headline makes this sound a lot worse than the article does.

From the article there’s basically a list of exemptions in the law that describes who doesn’t need to follow it (e.g. an online booking site for doctors visits), everybody else needs to check the rules to see if they do. And if they do, they then need to follow extra child safety rules (e.g. Roblox is opting out under-16s from open DMs by default)

GitHub can quite rightly say they don’t fall under the restrictions of the law, and that could be the end of it. The simple fact that it doesn’t have any form of private messaging feature is probably enough.

they’re just a radical left communist

God I wish that was remotely true

JXL is two separate image formats stuck together. An improved version of JPEG that can also losslessly and reversibly recode most existing JPEG images at a smaller size, and the PNG like format (evolved from FLIF/FUIF) that can do lossless or lossy encoding.

“VarDCT” (The improved JPEG) turns out to be good enough that the “Modular” mode (The FLIF/FUIF like one) isn’t needed much outside of lossless encoding. One neat feature of modular mode though is that it progressively encodes the image in different sizes, that is if you decode the stream as you read in bytes you start with a small version of the image and get progressively larger and larger output sizes until you get the original.

Why is that useful? Well you can encode a single high DPI image (e.g. 2x scale), and then clients on 1x scale monitors can just stop decoding the image at a certain point, and get a half sized image out of it. You don’t need separate per-DPI variants.

iirc the main reason for QOI was to have a simple format because “complexity is slow”, so by stripping things that the author didn’t consider important the idea was the resulting image format would be quicker and smaller than something like PNG or WebP.

Not sure how well that held up in practice, a lot of that complexity is actually necessary for a lot of use cases (e.g. you need colour profiles unless you’re only ever dealing with sRGB), and I remember a bunch of low hanging fruit optimisations for PNG encoders at the time that improved encoding speed by quite a bit.

AVIF is funny because they kept the worst aspects of WebP (lossy video based encoding), while removing the best (lossless mode) There was an attempt at WebP2, using AV1 and a proper lossless mode, but Google killed that off as well.

But hey, now that they’re releasing AV2 soon, we’ll eventually have an incompatible AVIF2 to deal with. Good thing they didn’t support JPEG-XL, it’d just be too confusing to have to deal with multiple formats.

Lossless is fine, lossy is worse than JPEG.