moon VS mandelbrot

(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/

It is my conviction that the Web Stack is the most capable, mature, accessible, and performant way of building and running UIs. It is the sheer amount of effort spent by millions of people around the globe that makes it the best UI stack for the vast majority of use cases. Some say that the browser nowadays is the most complex piece of software that few organizations can make. And it has been a while since Chrome super optimized runtimes are capable of running JavaScript at near-native speeds and the WebKit rendering engine is more than ready to generate each frame in under 8ms achieving 120 FPS.

Not long ago I have created a Mandelbrot set generator in 13 programming languages, Python included. Why not test the most recent version on runtime there? It is a CPU bound benchmark that demonstrates how performant a given language is at executing lots of math computations in nested loops.

I tested this hypothesis with Mandelbrot calculation. I.e. I have implemented the same algorithm twice, the only difference being different variable types:

mandelbrot.py - baseline implementation