Jon Pretty

lmao

See, other people start side projects and just abandon them. I only pitch ideas and wait for others to do the actual work...

i'll pitch you cargo-scala. or sbt but with "only" configuration on a build.toml file a tasks and plugins somewhere else.

NO TOML

So here's my pitch: declarative build definitions, tool exposes API for plugins to add/change anything they want in the build... but plugins are written externally in any language (presumably not in scala without native, or you'll die of waiting for all the cold starts)

fury already does most of these i think. Or plans to. Except you probably won't see the build definition in a file and the interactions with it are imperative (cc @propensive)

The interactions are imperative (like Git) and you won't see the file, but there's a new command in Fury to show you what it's going to build, step-by-step. I'm also going to add a command that prints the commands necessary to recreate a build, just because it will help learning.

I still wonder how conflict resolution is going to work