4 ms·

> In addition to the problems stated in the article that you're ignoring here What problems, exactly? The author acknowledged cargo works but hand-waves over v

> In addition to the problems stated in the article that you're ignoring here What problems, exactly? The author acknowledged cargo works but hand-waves over vague claims of "it does not track dependencies well or support arbitrary build graphs", followed by acknowledging those issues are either non-issues or solved problems whose solution was dismissed without any good reason (caching tools). The author's claims boil down to "I wanted to shoehorn Bazel but had no good reason to, so I double-down on Bazel's only selling point while ignoring everything". It's ok if anyone just wants to try stuff without having any rational or coherent argument to justify it, but let's not call that "problems".

pie_flavor 4y ago
The author gave a concrete example of such a build graph and a concrete example of why caching tools can't be used effectively.
- simplotek 4y ago
  > such a build graph Nonsense. All build systems implement a DAG of build targets. > why caching tools can't be used effectively Nonsense. There are a myriad of caching tools freely available, from ccache, sccache, build cache, etc. To get them to work, all you need to do is pass compiler launchers to them, which means setting a single env/build flag. The author is either trying hard to make a mountain out of irrelevant molehills, or is outright being disingenuous. Bazel is being sold as a solution desperately grasping at straw-like problems, while being feature incomplete.
  - pie_flavor 4y ago
    > All build systems implement a DAG of build targets. And the example they gave is one that doesn't work so well. > ccache, sccache, build cache, etc The example they gave included the build cache misfiring. ccache doesn't work with Rust. sccache does, but can't be used with incremental compilation or when building binaries, making it essentially useless for what they needed, i.e. speeding up CI and local dev. I really have no idea why you're still avoiding reading the article you're dismissing.

pie_flavor 4y ago

The author gave a concrete example of such a build graph and a concrete example of why caching tools can't be used effectively.

simplotek 4y ago
> such a build graph Nonsense. All build systems implement a DAG of build targets. > why caching tools can't be used effectively Nonsense. There are a myriad of caching tools freely available, from ccache, sccache, build cache, etc. To get them to work, all you need to do is pass compiler launchers to them, which means setting a single env/build flag. The author is either trying hard to make a mountain out of irrelevant molehills, or is outright being disingenuous. Bazel is being sold as a solution desperately grasping at straw-like problems, while being feature incomplete.
- pie_flavor 4y ago
  > All build systems implement a DAG of build targets. And the example they gave is one that doesn't work so well. > ccache, sccache, build cache, etc The example they gave included the build cache misfiring. ccache doesn't work with Rust. sccache does, but can't be used with incremental compilation or when building binaries, making it essentially useless for what they needed, i.e. speeding up CI and local dev. I really have no idea why you're still avoiding reading the article you're dismissing.