Jon Pretty

Personally I want an explanation about how it differs from Mill

It's based on source instead of binary artifacts

You mean Mill is configured via Scala whereas Fury is configured with something else?

Fury's configuration is data, not code (so it's static and fast). And configuration is done by running commands from the shell to modify the file.

So what I like with SBT is that I can write quickly tasks in Scala and convert them easily into plugins, even tho SBT's scoping is annoying. I feel like Fury won't let you do any of that but Mill do without the limitations of SBT.

With Fury you just write drive code with a main method and Fury can run it as part of the build. There's no reason why it can't depend on a library, so that's the equivalent of a "plugin".

You could even just depend on a library which provides its own main method and not write any code, if it's written that way. :)

And if I recall correctly you could have a single such place with 'plugins' in your workspace, shared between projects. Right?