Hacker News: xyse53

New comment by xyse53 in "[dead]"

xyse53 — Fri, 13 Feb 2026 14:26:48 +0000

This isn't just down, this discussion seems like it's been barely holding on and there's a non-zero chance it goes away or changes in some significant way moving forward.

New comment by xyse53 in "In praise of –dry-run"

xyse53 — Sun, 01 Feb 2026 02:23:15 +0000

Yeah I'm more of a `--wet-run` `-w` fan myself. But it does depend on how serious/annoying the opposite is.

New comment by xyse53 in "Kagi releases alpha version of Orion for Linux"

xyse53 — Fri, 09 Jan 2026 21:27:05 +0000

When you do release it, do you know yet if you plan on releasing the full change history? Or would you start with a snapshot at the ~release date?

New comment by xyse53 in "Netflix NFL streaming quality issues"

xyse53 — Fri, 26 Dec 2025 07:49:21 +0000

For an opposite datapoint: I had no issues with either game that I noticed. Denver area.

New comment by xyse53 in "Go-boot: bare metal Go UEFI boot manager"

xyse53 — Fri, 19 Dec 2025 03:05:48 +0000

It's also a good way to learn about UEFI for people most familiar with go.

New comment by xyse53 in "Samsung to halt SATA SSD production, leaker warns"

xyse53 — Mon, 15 Dec 2025 16:08:18 +0000

I get that for a boot / root drive but not for building a self hosted storage system. I'm not taking about cost of SATA SSD vs NVME; I haven't seen a lot of board+enclosure options that take enough M.2 disks.

New comment by xyse53 in "Samsung may end SATA SSD production soon"

xyse53 — Mon, 15 Dec 2025 16:02:20 +0000

I've noticed there aren't a lot of reasonable home/sb m.2 NVME NAS options for main boards and enclosures.

SATA SSD still seems like the way you have to go for a 5 to 8 drive system (boot disk + 4+ raid6).

New comment by xyse53 in "Building the largest known Kubernetes cluster"

xyse53 — Tue, 25 Nov 2025 04:07:15 +0000

I think it's possible to write a solid fuse filesystem. Not as performant as in-kernel but it could easily not be the bottleneck depending on the backend.

I commented though because GCP highlights it in a few places as component for AI workloads. I'm curious if anyone is using it in an important application and happy with it.

New comment by xyse53 in "Building the largest known Kubernetes cluster"

xyse53 — Mon, 24 Nov 2025 10:29:08 +0000

They mention GCS fuse. We've had nothing but performance and stability problems with this.

We treat it as a best effort alternative when native GCS access isn't possible.

New comment by xyse53 in "Microsoft updates flexible work expectations to three days a week in the office"

xyse53 — Tue, 09 Sep 2025 16:46:11 +0000

Is the current policy completely flexible? 2 days? (Or am I misreading and it's currently 100% in office?)

New comment by xyse53 in "QEMU 10.1.0"

xyse53 — Fri, 29 Aug 2025 05:06:26 +0000

I can't quantify how much of that surface is also reduced with the microvm machine vs other parts of QEMU vs Firecracker... But fair enough point.

New comment by xyse53 in "QEMU 10.1.0"

xyse53 — Wed, 27 Aug 2025 21:30:19 +0000

I've found QEMUs microvm to be faster at boot while having nicer tooling and a cleaner upgrade path if needing more features. Aside from hype I'm actually not sure why anyone would still use firecracker.

New comment by xyse53 in "FFmpeg 8.0 adds Whisper support"

xyse53 — Wed, 13 Aug 2025 15:46:55 +0000

My favorite is:

"Threesomes, with and without blame"

https://dl.acm.org/doi/10.1145/1570506.1570511

(From a professor I worked with a bit in grad school)

New comment by xyse53 in "I dumped Google for Kagi"

xyse53 — Tue, 05 Aug 2025 16:25:35 +0000

I want to stand on principle too. I switched from Google to Kagi about a year ago. If we're strictly comparing Google and Kagi, I consider Google far worse.

New comment by xyse53 in "GitHub pull requests were down"

xyse53 — Tue, 05 Aug 2025 16:21:01 +0000

Devs leaving can often be a stability boost :)

New comment by xyse53 in "Do not download the app, use the website"

xyse53 — Sat, 26 Jul 2025 06:11:11 +0000

I don't install apps for simple websites, ever.

Banking happens to be the one where I do keep the app for each bank/brokerage that I have an account with. Some of the features like mobile deposit work better. And the biometric login on Android is convenient when I'm looking up things quickly.

(I use the banking websites too, and for those prefer hardware passkey where supported, and if not everything else is in bitwarden).

New comment by xyse53 in "Uv: Running a script with dependencies"

xyse53 — Tue, 22 Jul 2025 01:43:12 +0000

I recommend trying it, it gets a ton of hype but I think for good reason.

This is the one.

New comment by xyse53 in "The borrowchecker is what I like the least about Rust"

xyse53 — Sun, 20 Jul 2025 00:32:51 +0000

I think that's harsh. IME Go excels in a business setting where the focus is on correct, performant, maintainable, business logic in larger organizations, that's easy to integrate with a bunch of other systems. You can't squeeze every last bit of low-level performance out of it but you can get ... 9x% of the way there with concurrent code that is easy to reason about.

New comment by xyse53 in "Linux and Secure Boot certificate expiration"

xyse53 — Fri, 18 Jul 2025 13:10:30 +0000

Yeah that's how my systems are set up. I also appreciate that each firmware let's me restore the original keys just in case without me having to manually back them up -- but they're not active for secure boot.

New comment by xyse53 in "Google is burying the web alive"

xyse53 — Mon, 26 May 2025 22:06:50 +0000

I find that yearly works better for me psychologically for stuff like this.

I got a 1 yr professional of kagi just to try it. IMO the results work. I've never seen Google do better when I compare; I have seen the Google AI responses be consistently straight up wrong.

To me it's worth the cost knowing I'm paying a sustainable rate for a service. Plus I want no part in whatever the hell Google is doing these days with search.