InvaderFizz

That is likely because of AWDL and your WiFi card doing channel hopping to listen between packets.

Set your channels to 6/149/37 and the lag will probably vanish. Exactly because of this, I only run those channels, even across multiple APs.

In Europe, you may need to use 44 instead of 149.

There is currently no good way to keep AWDL off other than a script that just turns it off every 200ms, because of course Apple. Also, not always an option with work issued Macs.

Same for me on macOS 15 on a M2. It's just Firefox, and I don't run much in the way of extensions there. Just 1Password and uBlock Origin.

I haven't noticed it lately, but that's because I've switched to almost exclusively Claude usage as of late.

When put in that context, it seems rather slow.

Still is. I made a basic http responder last week and it was under 4mb static compiled for a scratch docker container. I didn't even have to resort to compression, just stripped debug symbols.

I agree. Even within my own org there is some nitpicking, but it's almost always about style consistency for our shared codebase, which is valid.

If your PR doesn't pass lint checks, it doesn't get merged. And the only reason it would fail the lint checks is if your pre-commit hooks didn't fire.

There is no argument of 2,4,8 space vs tabs, because the code you commit is run through the linter.

Write however you want for the things that don't matter, the formatter always wins.

I run clusters on OKE, EKS, and GKE. Code overlap is like 99% with the only real differences all around ingress load balancers.

Kubernetes is what has provided us the abstraction layer to do multicloud in our SaaS. Once you are outside the k8s control plane, it is wildly different, but inside is very consistent.

32bit ARM and aarch64 are wildly different instruction sets. 32bit ARM may as well be x86 or MIPS as far as running it on aarch64 hardware, it is going to require just about the same level of emulation(memory models may be similar which would help, but that's about it).

Unlike x86/64, the 32bit silicon is entirely gone in most aarch64.

I'll review resumes of any referrals from my network. Usually provide tips or areas they need to show more substance in. I won't submit any network referral to my company's internal recruiter unless they stand out and fit a need.

The proximity to my network doesn't need to be strong, but your resume does.

Place it as a sell order on the trading book, above the current price. That way you are a market maker, and pay no fees.

50BTC is small potatoes, you aren't going to move the market.

It's not, but I'm saying you have the option to compare the two with an outside reference at the time of voting. You keeping the result on your phone after would be entirely your decision.

USB-C iPhones work with all kinds of USB-C hubs, devices, keyboards, mice, Ethernet adapters, etc out of the box.

As far as I have seen, USB-C on iOS devices has no authentication restrictions for anything.

The device in the article already has an iOS app, so while there may be a needed app entitlement, I don't think there are any showstoppers for making an iOS app for this particular thermal camera.

Which is what troubles me about making auditable digital voting systems. I'm not sure how you could do it while preserving the secret ballot.

About the best I can come up with is a QR code displayed on the screen and on a printout that you can compare with a third party phone app. Machine results are tabulated, and the QR code sheet is put in a lock box separately. This at least provides some way to compare what the computer says you voted versus the QR backup ballot for audits. I'm sure there are holes in my idea.

Reminds me of a group of friends that played call of duty together in the CoD4/WaW days. Individually we were mid-tier players on average. As a group, we completely dominated. We all knew each other's strengths, weaknesses, and general tactics. There was often no need to communicate specifics because we knew where each other would be and what we were doing.

We were always giddy when we got matched with a clan, especially if they were a mouthy crew.

I spend most of my time in the path of hurricanes, we lose power 5-10x per year for between 1 to 8 hrs on average.

When we lose power the battery backup for the modem takes over(15hrs runtime), and we have other portable batteries to recharge our phones multiple times.

If things get really bad, we can pull out the camping solar panels and keep the phones charged. At that point, I expect the fiber will be down anyways and cell service is probably all that would be available.

Works quite well. I can usually still complete my work day on my laptop without issue.

VRAM is such a small portion of the BOM that they could double it, keep the same margins, and the MSRP would only increase by like $300.

The problem isn't margin on the consumer cards, the problem is competing with their even higher margin workstation cards.

Sadly, you can drop "them" from your statement and its accuracy stays about the same.

Unfortunately, a side effect of the devaluation of the yen is that food quality at conbinis has decreased as they try to maintain price points. I recently spent a few weeks in Tokyo and there was noticeable difference in quality versus a few years ago.

This is really fun. A usability note, at least on Safari on iOS, you have to put the protocol for a web page to load. If you just put www.cnn.com without the https, it never loads.

Linux intentionally has an unstable driver ABI in part to make life a living hell for vendors who don't want to upstream their drivers.

Windows on the other hand maintains a very stable interface and has no desire to maintain vendor drivers.

Anecdotal, but I know the guys behind this. They're about as much free speech absolutists as you'll find. They're not going to remove anything unless it presents a large legal problem for them not to.

Additionally unless it's changed in the last six years, you should pretend ZFS dedupe doesn't exist.

I would agree with that. Given the history of the Oxide team, they chose what they viewed was the best technology for THEM, as maintainers. The rest is mostly justification of that.

That's just fine, as long as they're not choosing a clearly inferior long term option. The technically superior solution is not always the right solution for your organization given the priorities and capabilities of your team, and that's just fine! (I have no opinion on KVM vs bhyve, I don't know either deep enough to form one. I'm talking in general.)

I wouldn't worry about voice. They offer it as a paid feature of GSuite to business customers. It's not going anywhere.

I have the Twig and the triple blade. The twig is definitely my preferred. The triple blade is fine for shaving large areas, but any detail work and it's useless.

The twig does need to be cleaned very often, but it's not a big deal and it is better than any DE I have used in the past. Much less irritation and nicks than my DEs in the past.

> You cannot, for example, allow AWS Govcloud to handle SSL termination for ECS.

Are you saying you can't terminate TLS at the ALB in FedRAMP high and instead have to terminate TLS at the node/pod level? That's the exact opposite interpretation that we have taken.

Yes, TLS all the way at every layer, but we explicitly terminate at the ALB first.

I have not. I'm rarely in a country where that is available. Usually when I'm in the states, I'm not willing to experiment with it on my one week visit.

Your gut health has a direct impact on your lower back. If you are intolerant of some foods, when you inflame your gut, your lower back can end up in pain as well.

I'm intolerant of a milk protein. I can handle the bathroom consequences, I can't handle the lower back consequences.

I would guess it is to:

1. Build out a RISC-V ecosystem for almost zero cost. The value-add is quite large for a segment of potential buyers as they get the same excellent ecosystem, but can target RISC-V as the uArch.

2. De-risk dealing with ARM in the future as their moves in licensing changes foretell a bleak future for licensees

3. Eventually a bargaining chip with ARM on licensing. "Give us favorable terms, or we drop ARM from this design"

I liked everything except for how they just give up at the end. That annoyed me. Them not making it is fine, but them all giving up when it looked like there were many viable methods of escape annoyed me to no end. I still think it's the best Star Wars movie overall.

I've worked for security companies in different market segments to CrowdStrike. I was not at all surprised by how this went down. The "engineering" practices across the security vendors is practically Rube Goldberg of crap stacked on top of crap.