{
  "video_id": "reddit_1w4fp67",
  "channel_slug": "programming",
  "channel_handle": "r/programming",
  "title": "Bazel's UX is really, really, really bad",
  "url": "https://www.reddit.com/r/programming/comments/1w4fp67/bazels_ux_is_really_really_really_bad/",
  "external_url": "https://blog.appliedcomputing.io/p/bazels-ux-is-really-really-really",
  "upload_date": "20260901",
  "published_at": "2026-09-01T15:43:51+00:00",
  "transcript": "\n\n--- Top Comments ---\n\n\n[130 upvotes] I discussed Bazel with a fairly senior guy from Uber and his advice to me was \"don't bother unless you can afford dedicated resources for upkeep\"\n\n[62 upvotes] bazel doesn't scale down to one developer well. It's amazing for tens of thousands of developers thanks to its scalability and deep introspection capabilities. You can find and fix build graph problems at scale.\n\nThe previous version of blaze did a lot of things by convention and you couldn't trace them without leaky heuristics in some cases. Bazel is completely introspectable and deterministic.\n\n[51 upvotes] Just wait until you try to develop build rules.\n\n[47 upvotes] Having recently switched from CMake to Bazel I am worlds happier with Bazel. I don’t love it, but at least it’s not CMake. \n\nI really hate CMake. ",
  "transcript_chars": 820,
  "ingested_at": "2026-09-02T01:30:19.739164+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 205,
    "upvote_ratio": 0.9,
    "num_comments": 101,
    "author": "drmorr0",
    "is_self": false
  }
}