Hacker News Reader

> "just run `bazel run //amazing/server`" regardless of language and know that everything will magically work

> The major downside I've experienced is that any time you're trying to do something in a less-than-Bazel way (for example relying on binaries built outside of Bazel) things can get really hairy

Sounds like Nix

View on HN

As a nixpkgs maintainer I can't tell you how painful Bazel is for packagers. The difficulty of substituting dependencies. Unstable hashes of fetched dependency sources. The infeasibility of building bazel itself fully from source...

"substituting dependencies" sounds like an absolute nightmare for an upstream software provider.

Ah the upstream "we know everything and we will control everything" provider. Who doesn't maintain stable branches with security backports for their bundled dependencies, includes mystery binary dependencies, doesn't care about anything but the main two architectures, expects users to be fine with having seventeen copies of ffmpeg on their systems, will not let their tool work on a musl-based system...

Reply on news.ycombinator.com