xyse53

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.

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

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?

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

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

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.

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).

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.

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.

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

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.

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.

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)

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.

Devs leaving can often be a stability boost :)

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).

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

This is the one.

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.

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.

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.

I initially had a similar reaction, but there are so many cases like this for unit files. I think a higher level DSL for generating them would be useful.

I feel like I witnessed history because I happened to read the original reddit thread as it was happening. I can't find it now, might have been lost with imgur changes.

Some details here: https://www.howtobeadad.com/2012/11903/banana-added-for-scal...

Adding to the article (which I agree with): Lack of `uv pip install --user` has made transitioning our existing python environment a bit more challenging than I'd like, but not a deal breaker.

> Kubernetes Configuration Language ...

jsonnet? It would be nice if kubectl had native support but even without it find jsonnet incredibly useful and we use it extensively.

I replaced my Archers with glinet Flint 2 devices.

Funny, I just commented that I like the Roku method. My inputs show up as tiles on the home screen alongside the other apps. You can show/hide the ones you want.

I prefer Roku TVs at this point. No input button but the inputs are listed alongside the other apps on the home screen which works well for me.

I setup my vimrc about 15 to 20 years ago, and I haven't touched/cleaned it since.

It's not in the post but when this was rolled out internally at Google there was a corresponding builder struct to initialize from.

https://en.m.wikipedia.org/wiki/Evi_Nemeth was part of the early development of sudo. I did a double take years ago running "The Woz Lab" at CU Boulder, reading the sudoers man page and seeing the 128.138 address space in the examples that I was managing subnets of.