cls59

Yeah, the GitHub integration is definitely "click button, sign in to GitHub, automation sets everything up" which is simple and hands-off.

But, the wrangler CLI isn't that much of a step up. Biggest items are installing the CLI and having the CloudFlare API token available in a secure manner.

The official Cloudflare CLI can ship static site content with one command: "wrangler pages deploy"

Easy enough to run from another CI or automated system.

Tailscale automates wireguard key distribution and then layers routing, DNS, network ACLs, and other niceties on top.

For example, you can create a token that grants VPN access with inbound SSH as the only allowed traffic. Add that as a secret to GitHub Actions and now you can ad-hoc debug failing CI via `tailscale ssh`.

Same! Although, for Headplane you may need at least 1GB of RAM.

Headscale turns the $5 VPS into the thing that connects my laptop to my other compute resources while I am out and about.

Linux Desktops are having a moment this year, but there are still all sorts of sharp edges that a user has to navigate.

Getting a laptop to properly hibernate such that the battery life is usable on the road is a whole roll-your-own-adventure.

WirePlumber apparently mis-classifies some headphones resulting in only input or output working in web meetings.

I've worked with Linux on the server side for over 20 years and these were just two Fedora issues that LLMs helped me sort out recently. If I had to spend a whole day debugging these items, I would likely be drifting back towards macOS or WSL2.

Getting Linux installed has always been the "easy" part. It's everything after that in daily operations that has been hard.

Even with copy-on-write, fork() still has to pay the setup cost for COW. If the parent process has a lot of busy threads (e.g. Java), you can end up doing a lot of unnecessary COW before exec() fires.

If Apple keeps using A Pro-series chips for the Neo, then the RAM will go to at least 12GB when they swap to the A19 Pro, or newer.

Or Dow Chemical.

If I understand the article correctly, that second proof was published as a rider on a first proof that was entirely Dedekind's. So, there was definitely a credit owed at time of publishing.

I came away with the impression that the biggest villain in this story was Kronecker. Without the need to tiptoe around his ego and gatekeeping, these results may have been published as a paper with joint authorship.

The fact that it was even proposed in the first place is still concerning.

From a quick skim of hardware support on Wikipedia, it looks like encoding support for H.265 showed up in NVIDIA, AMD, et. al around 2015 whereas AV1 support didn't arrive until 2022.

So, the apparent preference could simply be 5+ years more time to do hardware-assisted transcoding.

Agreed. I think the buried lede here is actually the clawback clause. With that in the contract, this isn't a $1.5 million dollar grant, it's a $1.5 million dollar liability.

If you take the money and spend it on research and development and then get hit by a clawback, whether due to "DEI" or some other reason, that is a financially ruinous event to somehow come up with $1.5 million dollars that was already spent.

A shame and a waste as it sounds like the project would have been beneficial outside of the Python ecosystem, had it been funded.

Also, "git reflog" lists out all commit SHAs in chronological order. Trying to figure out how to rebase, but got lost and everything seems broken? You're just one "git reset" away from the better place you were in and "reflog" has the list.

> It doesn’t make sense to tax every other passenger for it.

I'd rather pay a monetary tax on my ticket to keep families organized together instead of the discomfort tax of sharing a row with parent+child that has been unexpectedly split up from their partner and is now trying to manage the child's behavior for the duration of the flight without the benefit of teamwork.