node_crunch VS goreleaser

I've written my own crate called node-crunch for distributed computing.

This looks really nice! It has encryption and compression is planned for the next release. I've developed node_crunch, a crate for distributed computing and designed the protocols myself. I think that Zenoh could make my life a lot easier ;-) I'll definitely try it out!

You may be interested in darwin-rs, a crate for evolutionary algorithm that I'm working on. It uses multiple threads to speed things up, but I'm currently implementing node-crunch support, so that it can run on a cluster.

Nice! I'm currently working on node_crunch a crate for distributed computing. I've modified an existing ray tracer to run on a cluster. If you're interested you can have a look at the code.

I'm currently working on node_crunch.

> This is a much faster way than setting up Github Actions to build an executable for every possible platform on every release

It's not even that hard. Just use GoReleaser.

https://goreleaser.com/

I also got my eyes on GoReleaser, which I will use in my (Go) projects.

With "xq", I went even further and automated the release process using GoReleaser. To publish a new release, the only thing I need is to create and push the Git tag. The corresponding GitHub Action will trigger a release process, and GoReleaser prepares the binaries and changelog based on declared conventions. The result has a high level of predictability, and no manual work is required.

Things I can't live without in a new Go project in no particular order:

- https://github.com/golangci/golangci-lint - meta-linter

- https://goreleaser.com - automate release workflows

- https://magefile.org - build tool that can version your tools

- https://github.com/ory/dockertest/v3 - run containers for e2e testing

- https://github.com/ecordell/optgen - generate functional options

- https://golang.org/x/tools/cmd/stringer - generate String()

- https://mvdan.cc/gofumpt - stricter gofmt

- https://github.com/stretchr/testify - test assertion library

- https://github.com/rs/zerolog - logging

- https://github.com/spf13/cobra - CLI framework

FWIW, I just lifted all the tools we use for https://github.com/authzed/spicedb

We've also written some custom linters that might be useful for other folks: https://github.com/authzed/spicedb/tree/main/tools/analyzers

Goreleaser is nice. https://goreleaser.com/

I use goreleaser for packaging my binaries. I'm not currently doing RPM, but it does a lot of services and if you don't hunker down on a single solution, it might help with keeping your releases up to date/in sync.

There's some packaging issues, for example, we've always wanted to publish deb/rpm packages, but never got around to adding it to either promu or completely switching our build tooling over to GoReleaser.