Nvme drive controllers already throttle at the drive level but the interface gets hot now, and client devices can’t negatiate slower interface speeds afaik

WIAE?

Nike

Source?

Why use for lowercase?

I believe that’s Intel only, AMD’s isn’t internet connected

Based nasa compliant engineer

You create a pod and bring the pod up

As linus says, if you need to use a debugger your code is too complicated

Some guy posted a short thesis for crowdstrike just hours before the thing happened

Clearly user error

Don’t forget when they bribed Dell with 1 billion dollars per year to not build any AMD laptops

I think you should have used ADB to boot from the other A/B partition

The devs said there will never be any newer versions after this release, maintenance only

Bingo, and if the latest mesa breaks your app for example, you can target an older one until it’s fixed instead of end users having to fuck around downgrading system packages

Flatpak solves the problem with targetable platform versions, you just update the manifest for your app every like 6-12 months to target the new one

You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia’s or mesa’s opengl?

You cannot statically link everything. Take graphics libraries and APIs for example, do you statically link against nvidia’s or mesa’s opengl?

Why?

I use appjails to containerise my apps like jellyfin, it’s similar to docker but simpler and more powerful (docker does not support freebsd)