kminehart

This isn't resilient to this downtime though. Our self-hosted runners are currently not functioning because of some github dependency.

Are there any GitHub Actions-compatible CI services out there that don't rely on their infrastructure? I know of depot's but no others; are these resilient to these outages or do they still lose functionality? I imagine the latter but I don't know.

I can definitely relate to the abstract at least. While I am more productive now, and I am way more excited about working on longer term projects (especially by myself), I have found that the minutia is way more strenuous than it was before. I think that inhibits my ability to review what the LLM is producing.

I haven't been diagnosed with ADHD or anything but i also haven't been tested for it. It's something I have considered but I think it's pretty underdiagnosed in Spain.

And Coca Cola

I walked away with that page open, glanced at the "Is it time to rewrite sudo in Zig?" post, and clicked to see the comments because I thought it was real :')

I can already tell by their example that I don't like it. I've worked with a bunch of different container-based CI systems and I'm getting a little tired seeing the same approach by done slightly differently.

    steps:
      - name: backend
        image: golang
        commands:
          - go build
          - go test
      - name: frontend
        image: node
        commands:
          - npm install
          - npm run test
          - npm run build

Yes, it's easy to read and understand and it's container based, so it's easy to extend. I could probably intuitively add on to this. I can't say the same for GitHub, so it has that going for it.

But the moment things start to get a little complex then that's when the waste starts happening. Eventually you're going to want to _do_ something with the artifacts being built, right? So what does that look like?

Immediately that's when problems start showing up...

- You'll probably need a separate workflow that defines the same thing, but again, only this time combining them into a Docker image or a package.

    - I am only now realizing that woodpecker is a fork of Drone. This was a huuuge issue in Drone. We ended up using Starlark to generate our drone yaml because it lacked any kind of reusability and that was a big headche.

- If I were to only change a `frontend` file or a `backend` file, then I'm probably going to end up wasting time and compute rebuilding the same artifacts over and over.

    - GitHub's free component honestly hurts itself here. I don't have to care about waste if it's mostly free anyways.

- Running locally using the local backend... looks like a huge chore. In Drone this was basically impossible.

I really wish someone would take a step back and really think about the problems being solved here and where the current tooling fails us. I don't see much effort being put into the things that really suck about github actions (at least for me): legibility, waste, and the feedback loop.

There's a few things for me, and the saddest part is I'm a very die-hard Linux user. Until a couple months ago when I had to start traveling, I've been using Linux exclusively for work.

1. The battery life, as others have mentioned.

2. The quality of the hardware: The screen is incredibly nice, the trackpad is VERY nice to use, and no other laptop has even come close.

3. It's so quiet. The fans almost never spin unless I've been compiling something for over a minute. I don't know how they do it but any other Linux laptop I've used, including desktops, have been super loud when running similar tasks.

I used to sharpen my straight-knife planer blades, planing irons, chisels, and knives with whetstones / water stones. It was too big of a pain in the ass over time, so I switched to diamond stones.

Biggest advantages is that you don't need to pre-soak them and diamond stones don't develop a valley / have to be flattened.

if you plan on getting into sharpening I would just start with a coarse, fine, and extra fine diamond stone and a leather strop w/ stropping compound.

also don't forget how quiet this thing is.

Before their arm64 CPUs you could get a thinkpad or an xps and not have really bad FOMO. But now... it's just not even close :\

> Finding a laptop that works well is annoying, however.

It doesn't exist at the moment. :\

I would pay 2x the price of a macbook for a linux laptop with the same hardware quality.

The battery life and power/efficiency of my m4 pro is insane. It's so good that it's really hard to justify using anything else right now.

I don't have a link for it yet, but I am working on using an HCL-like syntax to write CI pipelines. Ideally it would function a lot like dagger but written a lot like terraform.

The main problems that I want to solve are the really slow feedback loop of complex GitHub Actions / GitLab CI, but without the limitation of having to run it within another CI provider.

If I was in charge of our infra automation I would have done this. We opted for jsonnet instead which is an absolute nightmare, or at least the way we've set it up is.