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.

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

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.

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

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.

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.

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.

here's a closer look at it with a microscope. https://www.youtube.com/watch?v=Y4ReQ83CZOQ

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.

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.

I think that a bigger factor is the car-centric city and suburb design that started in the US after World War II. It was intended to give everyone what they wanted; a big house, a yard, consistency, etc., but it prevents anyone without a driver or a car & license from socializing and visiting a "third place." I think that it increased individual isolation even before the internet or social media existed and thus set the foundation for social media to be as big of an influence as it is.

They definitely promise the same thing but with different approaches.

The key thing that turned me off of Dagger is this: "Tie it all together in CUE". Personally I'm not the biggest fan of CUE and would rather just write Go. Correct me if I'm wrong but it seems like CUE is used in Dagger to create the config that the CI service will use. Switching to another service would mean rewriting that CUE file but reusing the Go/JS/whatever components, which is a great improvement over what we have to deal with now. With Scribe the goal is that you'd only ever have to write the whole thing once, but you're limited to Go.

I'm happy to answer any questions. Please let me know what you think of the idea and if there's anything you'd like to see.

Comments URL: https://news.ycombinator.com/item?id=32185728

Points: 25

# Comments: 2