moon VS roadmap

(for context - I'm not interested in first class node support)

This seems pretty cool. I particularly like how 'gradual' it seems to be relative to things like Bazel, i.e. you can take some shell scripts and migrate things over. I did have a play and hit an initial problem around project caching I think, which I raised at [0].

One comment, from the paranoid point of view of someone who has built distributed caching build systems before is that your caching is very pessimistic! I understand why you hash outputs by default (as well as inputs), but I think that will massively reduce hit rate a lot of the time when it may not be necessary? I raised [1].

As an aside, I do wish build systems moved beyond the 'file-based' approach to inputs/outputs to something more abstract/extensible. For example, when creating docker images I'd prefer to define an extension that informs the build system of the docker image hash, rather than create marker files on disk (the same is true of initiating rebuilds on environment variable change, which I see moon has some limited support for). It just feels like language agnostic build systems saw the file-based nature of Make and said 'good enough for us' (honorable mention to Shake, which is an exception [2]).

[0] https://github.com/moonrepo/moon/issues/637

There are many tools like Lerna, Nx, Turborepo, Moon, Rush, and Bazel, to name a few. Today, we'll be using Turborepo, as it's lightweight, flexible, and easy to use.

You should give moon a try: https://moonrepo.dev/

x86-64 containers?

https://github.com/docker/roadmap/issues/384 is still open. :(

Request features or give feedback: https://github.com/docker/roadmap/issues/524

Nothing in the road map [Github] returned by searching 'stop'.

Further reading online revealed that host network mode is not available for swarm started with docker stack deploy. (Possible related open issue: github link).

Single-click k8s install. Extensions. Init. And there are people who just prefer an app-based experience for their own reasons - I think it was the most "upvoted" request ever on their public roadmap.

In case you need to run x86 containers: Docker has Rosetta support now but it's buggy.

https://github.com/docker/roadmap/issues/384

Without Rosetta it uses relatively slow Qemu emulation.

https://github.com/docker/roadmap/issues/44

So, at the moment, any public organization images are doomed to be lost, if they won't pay.

I've been watching this GitHub issue for damn near 3 years. Filesystem performance is pretty bad, depending on what you're doing. I had to kludge together workarounds to my DX at my last role where we used Docker for development. It was really, really painful and distracting.

[2] https://github.com/docker/roadmap/issues/7