Recent submissions

Comment · 1 day ago
This doesn't work if the pulls are happening in swarms of ephemeral sandboxes.

Also, maybe FUD, but is there anything useful to learn from (p)npm other than cautionary tales?

Comment · 8 months ago
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.
Comment · 9 months ago
Yeah I'm more of a `--wet-run` `-w` fan myself. But it does depend on how serious/annoying the opposite is.
Comment · 9 months ago
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?
Comment · 10 months ago
For an opposite datapoint: I had no issues with either game that I noticed. Denver area.
Comment · 10 months ago
It's also a good way to learn about UEFI for people most familiar with go.
Comment · 10 months ago
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.
Comment · 10 months ago
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).

Comment · 11 months ago
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.

Comment · 11 months ago
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.

Comment · 1 year ago
Is the current policy completely flexible? 2 days? (Or am I misreading and it's currently 100% in office?)
Comment · 1 year ago
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.
Comment · 1 year ago
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.
Comment · 1 year ago
Comment · 1 year ago
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.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton