On Rendering Diffs

This new code viewer wowed the nerds, confused a few, and even sparked layout rescue tips

TLDR: Pierre showed off a new web tool that makes huge code changes easier to read without the page slowing to a crawl. Commenters were impressed, but some immediately asked for better ideas on how changes are shown, while others roasted the site layout and crooked ASCII art.

A small software company dropped a big flex: a new browser-based tool called CodeView that claims it can open giant code changes almost instantly, even when other review pages start wheezing. The post itself is a deep dive into why huge change lists become painful to read online, and how Pierre’s team tried to fix that with smarter loading and smoother scrolling. In plain English: they want people reviewing code to actually see the whole mess without the website turning into soup.

But the real show was in the comments, where the crowd split into three classic internet camps: the impressed, the picky, and the comedians. One fan was ready to hand Pierre the crown immediately, basically saying GitHub and GitLab could never and begging for this to land in Forgejo instead. That’s the kind of compliment that doubles as a drag. Another commenter came in with the ultimate nerd plot twist: cool performance tricks, sure, but why not talk more about how changes should be shown in the first place? Translation: nice engine, but what about the steering wheel? And then there was the chaos goblin energy everyone secretly loves — one person posted a browser-console fix for the site layout, while another zeroed in on the article’s slightly crooked ASCII art header like it was a crime scene. So yes, Pierre launched a serious tool, but the community turned it into a mix of applause, unsolicited product advice, and gentle roast comedy.

Key Points

  • The article describes how large pull requests can make existing code review interfaces slow, fragmented, or difficult to navigate.
  • Pierre says it released Diffs about six months earlier to provide code and diff rendering components for teams.
  • The initial Diffs release included `File` and `FileDiff`, followed by a simple virtualizer and an API for moving syntax highlighting into worker threads.
  • The article says those optimizations did not fully solve complexity, memory usage, and virtualization blanking issues at scale.
  • Pierre built CodeView as a virtualization-first component intended to make rendering very large diffs in the browser practical, and demonstrates it through DiffsHub and the `@pierre/diffs` package.

Hottest takes

"I doubt Github or Gitlab would ever do something as good as this" — IshKebab
"I was hoping that this would talk more about the logic behind generating a diff" — joosters
"the header ascii art is suspiciously misaligned... :^)" — logdahl
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.