{
  "video_id": "reddit_1w630ne",
  "channel_slug": "programming",
  "channel_handle": "r/programming",
  "title": "Branch‑Avoidant Programming",
  "url": "https://www.reddit.com/r/programming/comments/1w630ne/branchavoidant_programming/",
  "external_url": "https://easylang.online/blog/branchless",
  "upload_date": "20260903",
  "published_at": "2026-09-03T10:00:28+00:00",
  "transcript": "\n\n--- Top Comments ---\n\n\n[25 upvotes] You don't actually need to avoid branches, you just need to make sure that most of the ones you have are very predictable, then their impact is not that big... Same with memory accesses and most other things... The more predictable, the better...\n\n[13 upvotes] That's interesting. Would this also apply to higher languages, like Java, which run on a JVM? (Not intending to rewrite my code, but I'm curious how much languages like Java benefit from branch prediction and brancheless approaches)\n\n[10 upvotes] Interesting, I like the assembly comparison. I got a couple of questions / thoughts:\n\nWouldn’t the if statement make it easier to read? \n\nWouldn’t an if statement allow for early returns?\n\nI guess if an optimization is needed this technique can be considered. \n\nAnyways good post non the less, thanks for posting:) ",
  "transcript_chars": 861,
  "ingested_at": "2026-09-03T13:30:19.712373+00:00",
  "source": "reddit",
  "yt_meta": {
    "score": 105,
    "upvote_ratio": 0.92,
    "num_comments": 45,
    "author": "fagnerbrack",
    "is_self": false
  }
}