made you look
AVIF is generally smaller in size than both WebP and PNG. AVIF supports animation while PNG does not.
The lossless mode in AVIF is so bad that a BMP in a ZIP file produces smaller results.
Which makes sense, as it doesn’t actually have a dedicated lossless mode (like WebP does), the encoder is just to not quantise the video data it produces.
JXL can do lossy images (like JPEG) and lossless ones (like PNG), and on average it’ll produce smaller file sizes than both (While beating JPEG quality wise). The killer feature is that it can do lossless recompression of existing JPEG files and shave off about 20% of the file size, and it’s reversible so you can turn those JXL files back into JPEG images for existing software.
The downside is that it was created by Google Research (among others), but the Chrome team made AVIF instead and decided that’s what they’d support and nothing else.
At least Safari supports it.
For a community called “technology” there’s a pretty strong anti-AI bubble going on here.
Are you surprised people have opinions about technology, in a community dedicated to discussing technology?
Use Zola or Hugo then
As I was doing that, I also thought I’d message the vendor and ask them if they could share any specifications or docs regarding their protocol. To my surprise, Nanoleaf tech support responded to me within 4 hours, with a full description of the protocol that’s used both by the Desk Dock as well as their RGB strips.
Now that is cool.
And on the upside for them, no Gnome, since the devs are making systemd a hard dependency.
I am entirely unsurprised that people who hate systemd also hate wayland.
Then there’s accessibility functions, which wayland breaks almost by design by denying apps access to each other. Even something as simple as an on screen keyboard becomes nearly impossible to implement.
That’s a side effect of just dumping everything into X11, once you switch from it you lose all the random kitchen sink warts it grew over the years.
Like an on-screen keyboard shouldn’t be fiddling with a display protocol to fake keyboard inputs, it should be using the actual OS input layer to emulate them (So then it’d work with devices that read input directly and not go via X11). Same with accessibility, there’s a reason other OSs use separate communication channels with their own protocol.
Tizen (resting place of Meego)
I’d say SailfishOS is the final resting place of MeeGo, especially since it’s maintained by ex-Nokia devs.
So how the OS already catches links to e.g. YouTube and offers to open it directly in the app, it could also do that for apps that weren’t installed and it’d just download and run them automatically. One of the examples was Vimeo, instead of loading the website it’d download a cut down variant of the normal app and load the video in that instead.
The idea was to push people towards using apps instead, but now Google control the web they can just make that their app store instead, so native apps aren’t as relevant anymore.
And there’s still web directories hanging around, similar to the now dead dmoz site.
https://url.town/ and https://curlie.org/ for example
True, that’d definitely make it a lot more viable to hold corporations to account.
It’s an easy license to reason about, allows for basically any project to use it, and you don’t need to worry about trying to enforce it (Because the GPL is only as good as your lawyers are)
We were mistaken as the entry for Austria and nobody wants to admit that mistake
Plan 9 is inspired by UNIX (Helps that it had the same devs), but it’s not a direct continuation.
UnixWare is I think the only direct continuation of the original AT&T UNIX. The various BSDs are close enough but were re-written entirely in the late 80s/early 90s so there’s nothing original remaining.
Should be possible, as it’s a normal VM you can already install flatpak apps in said VM as normal, you’d just need a Windows side bit to invoke the install within WSL when you opened the flatpak bundle, and then something to add a start menu shortcut from the app inside the VM (Which I actually assume already exists, I never actually ran WSL2 when I was on Windows)
Why have a laptop or a dual boot with Linux when you can now more easily stay on the proprietary OS ?
This is called market retention.
Preventing migration to another OS, another software ecosystem.
The ‘Embrace’ and ‘Extend’ parts of EEE.
That’s stretching the definition to the point it’s nearly unrecognisable.
What the term meant was for things like Internet Explorer, where MS adopted an existing standard (Embrace), started changing it in incompatible ways (Extend), while using their market power to lock out competitors (Extinguish)
e.g. IE used an incompatible method for sizing and laying out elements than any other browser, so a site that laid out properly in NN4 looked broken in IE6, and vise versa. So most devs targeted IE6 as it was more popular, and NN4 users got more and more broken sites.
ACPI was similar, Windows had an extremely lax implementation of it, so motherboards often shipped with bugs that Windows would ignore but would stop anything else from booting. Intentional? Doesn’t really matter, since it sure was helpful in slowing the adoption of things like Linux, that had to come up with workarounds for all the broken hardware.
Not like you can fork it to run on a different OS.
For WSL1? yep that’s effectively impossible.
WSL2 is effectively just a wrapper around the kernel virtualization support and a bundling format, as long as whatever image you run talks to the host properly (like any other virtualised OS would) it’d run.
He could have tried to fight the order, that’s what the previous management used to do.
So it depends on the specific HDR encoding used, Rec2020 is the most common ones you’ll see (It’s meant for “pure” setups, i.e. where the source and output are tightly linked, e.g. gaming consoles or blu-ray, or so) and the raw data won’t look great. While something like HLG (Hybrid-Log Gamma) is designed for better fallback (As it’s meant for TV broadcast, where the output device is “whatever TV the user has”), so should just look dimmer.
This is a HDR screenshot I took of Destiny 2, which uses Rec2020, tone mapped to SDR
And here’s the raw screenshot data from before tonemapping.
If the second image had all the right HDR metadata, and the viewer supported it properly, then both images would match.