Viewing profile — ndmitchell

Neil from the Buck2 team here. I think your points are pretty much spot on - everything we use internally is battle tested, everything we don't is less tested. We've tried to use t…

We schedule tasks mostly using tokio - without any particular care. It's mostly good, but occasionally causes some performance headaches. I think in the fullness of time we might n…

I think of Shake as a library for implementing build systems, and was hoping that libraries would emerge that described how to implement rules like C++, and how they should compose…

Thanks for the comments! There are two levels at which you could make Buck2/Bazel compatible: * At the BUILD/BUCK file level. I imagine you can get close, but there are details bet…

There's no such thing as a phony target, but there is both `buck2 build` and `buck2 run` - each target can say how to run and how to build it separately. So you can have a shell sc…

These were from an open source contributor - out the box Buck2 doesn't really have support for Nix. But because the rules are flexible, you can write your own version of Nix-aware …

It can use watchman, but for open source we default to inotify (and platform equivalent versions on Mac/Windows) to avoid you having to install anything.

> Until they re-implement it again :) As the paper says, every previous implementation started nicely and got horrible towards the end. This time, that hasn't happened, so _hopeful…

The old GHC build system did do everything in 3 phases. And they were pretty magic phases. It's not clear there's any upper bound on the number of phases, and maintaining each phas…