hurricanepootis

Redox: Reduction and Oxidation

You'd be surprised. The only things conservative americans that lives in their isolated suburbs care about are gas prices and whether or not they can buy the new iphone for cheap.

I believe the purpose of Zink is that if someone is writing a new driver for a new GPU, they only need to write a Vulkan driver. After all, OpenGL is a legacy API. Still has lots of uses. But, I think it's better if the effort to write a new driver is spent on bringing up just a Vulkan implementation instead of needing to write two drivers of once.

It's kind of like how Mesa's existing OpenGL drivers all switched to Gallium3D, which splits the Graphics driver into an agnostic front-end and a device-specific backend. Allows for a lot of re-use and optimization. I heard they're wanting to do something the same with their Vulkan drivers for the future as well.

I think it has the potential to be pretty good, especially on modern hardware. If using DXVK or VKD3D is any indication, I think the performance losses can be minimized. Plus, I've used Zink before on Mesa's RADV Vulkan driver, and it's pretty good.

Looks like Intel is choosing to title its new crescent island cards with the D prefix despite being Crescent Island.

Kind of disappointed that Intel is (probably) not going to release consumer class GPUs. Intel's driver stack was seriously getting mature—both on Linux and Windows. It's always nice to have a third option available.

Honestly, what's stopping a high rise building from doing an internal GPON/XGS-PON distribution to all the buildings inside?

I hope Qualcomm upstreams all the device tree kernel level stuff to Linux for every laptop model. One of the things I don't like about Arm Laptops is—for example—how even if a SoC is supported upstream, if the manufacturer does not upload a device tree for their device, then you're cooked.

I read that while these Snapdragon laptops do technically have UEFI + ACPI, the information they provide is not useful for Linux and is more coupled with Qualcomm's proprietary drivers on Windows. Therefore, device trees are needed on Linux (I could be wrong about the first part).

The actual app and binary is called koko, but shows up as "Photos" cause it's named that in the desktop file.

Asahi linux has been going on for a few years now

So, looks like SteamDB is gonna get a billion features behind paywall. Probably gonna rate limit how many depots you can look up for free within the hour lol

Realtek wifi chips suck, their drivers are always buggy

> household hasn't burned through a full tank in the months since. They may have killed the EV subsidies in the US but they just went out and created a huge regressive tax on everyone not driving an EV.

Modern fuel blends are usually 10-15% ethanol. Ethanol is an alcohol, and thus is able to absorb ambient water from the air into the gasoline solution. Gasoline stored for a long time will generally increase in water content (if I am not mistaken lol), thus it maybe for future reference, try to avoid ethanol based fuels if possible if you're not gonna be using your ICE car. It's like how people who store their motorcycles or fancy performance cars during the winter leave it without fuel, or add a fuel stabilizer.

As someone who learned the double bass in school, jumping to bass guitar & guitar was super easy cause of the fourth tuning intervals. Anytime I ever jumped on cello, it was a nightmare cause all of the sort of "relationships" between the current note I was playing and other notes were totally different.

I'm on KDE 6, and I don't have a ~/.kde. I think now a days, KDE uses ~/.config and ~/.local/share. Honestly, sometimes I wish the KDE Frameworks had a thing like Dconf, so apps can store their configurations inside of a database instead of barfing everything out into a ~/.config folder.