There are two things which make writing builds in Fury difficult. The first is that it still has bugs. These will be fixed. The other is that nobody has any experience with it. This will be fixed too.
-
What niche is this aimed at that isn't covered by sbt, cbt, mill, gradle, pants, etc...?
I wouldn't call it a niche. Fury has a different design to any of those other tools: Builds are represented by data (not code); dependencies are sources; builds are defined externally; interaction is through a CLI; it could potentially fix binary dependency hell.
-
-
Assuming, developers using Fury will not have programmatic control unlike sbt. Please correct me.
-
There are currently no plans to offer programmatic control, but I haven't ruled it out. Ultimately, I don't have a use-case for it yet, but that's not to say one won't ever arise.
- Show replies
New conversation -
-
-
I still want to see if/how to integrate it with Bazel. Bazel is great for building from source, managing external dependencies not so much.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.