July 20, 2026
Canvas wins, comments sting
We rewrote our custom visualisation renderers from SVG to be in Canvas
They ditched the browser clutter, but commenters got hung up on the vibes
TLDR: The team says its dashboard is much faster after replacing a browser-heavy drawing method with one that paints directly to the screen. But the biggest reaction wasn’t praise for speed — it was a sharp accusation that the post itself felt AI-written, turning a performance story into a vibes debate.
A company says it made its profiling dashboard dramatically faster by swapping SVG (a way of drawing with lots of separate browser elements) for Canvas (a way of painting directly onto the page like a digital sketchpad). In plain English: instead of asking your browser to babysit tens of thousands of tiny boxes and labels, it now just paints the picture and moves on. The result, they say, is that zooming, scrolling, and resetting now feel basically instant.
But in the comments, the real fireworks weren’t about speed numbers — they were about authenticity. The standout reaction came from a reader who basically said, yes, the approach is interesting, but this absolutely looks like Claude wrote it. Ouch. That instantly shifts the mood from “wow, nice performance win” to “hang on, are we reading an engineering post or an AI-generated brand brochure?” It’s a classic internet plot twist: the team is celebrating a big under-the-hood upgrade, and the crowd is side-eyeing the tone, the visuals, and whether the whole thing feels a little too polished.
That makes this one less of a dry coding update and more of a style-on-trial moment. The hottest take isn’t “Canvas beats SVG,” it’s “Sure, but who’s actually talking here?” In other words: the software got leaner, while the comments got shadier. And honestly, that’s the part people will remember.
Key Points
- •The article reports that the profiling dashboard's flame graph renderer was rewritten from SVG to Canvas to improve performance.
- •An earlier SVG optimization reduced initial rendering of a large query from around eight seconds to about 91 milliseconds, but SVG still faced scaling limits from DOM node overhead.
- •In the old approach, each flame graph frame created SVG DOM elements, causing the browser to spend time on styling, layout, painting, and garbage collection.
- •The Canvas-based renderer removes per-frame DOM elements and objects, which the article says makes zooming, resetting, and scrolling feel instant.
- •The backend was rewritten in Rust so flame graphs can be produced through a composable SQL function and streamed as columnar Arrow data.