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's the relative importance/priority of bootstrapping a run-of-the-mill sbt build into a fury build? I would think that would be an accelerant.
Right now most complexity is a consequence of the availability of other libraries. Most don't exist for Fury yet, so the priority is getting common libraries converted to use Fury so people can depend on them easily.
-
-
Scodec is a pretty good example of a run-of-the-mill build. It has dependencies on shapeless and scodec-bits. I had to convert scodec-bits. It was hard because of bugs I had to fix. Writing the build (for one Scala release, no benchmarks/tests) took five minutes; no exaggeration.
-
Yeah I see. But it might be something worth developing in parallel (perhaps by someone else on the dev team) and releasing publically when feel featured.
End of conversation
New conversation -
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.