DUB - call to arms

[Nick Sabalausky (Abscissa)]

On 4/15/19 12:37 PM, Nick Sabalausky (Abscissa) wrote:
> I've personally put a lot of effort into trying to fix DUB's problems in 
> the past. Though I would be happy to be proven wrong, at this point, I'm 
> all but convinced the problems with DUB are far too fundamental.
> 
> I know this is the sort of proposal that makes people cringe, and often 
> for good reason, but in this case, I really do think it would be 
> quicker, easier, and produce a better result to simply re-design it from 
> the ground up (while making sure to leverage the existing code.dlang.org 
> ecosystem in some say), than to try to wrangle this 600lb gorilla into 
> something it was never designed to be.
> 
> I've long been hoping to take a stab at this myself, and I often find 
> myself thinking through details of how it would work. I would, however, 
> need help with the dependency-resolution algorithm (perhaps somebody 
> could go into DUB and work to decouple its dep resolution algoritms from 
> the rest DUB as much as possible - or at least document how to interface 
> with it as a lib).

To clarify, I'm mainly referring to the "package manager" aspect of DUB 
here. I'm less concerned with the "buildsystem" part simply because with 
a proper package manager, individual projects and even libraries will be 
free to use whatever buildsystem they want, even if that happens to be 
"dub build" (which *is* an entirely reasonable choice for many simpler 
projects...in large part because that's specifically the use-case it was 
primarily designed for.).