2019-04-08
2023
#html
Alvin Wan
219
Apr 8, 2019 ⋅ 7 min read

When to use HTML5’s canvas

Alvin Wan PhD in artificial intelligence at UC Berkeley, focusing on small neural networks in perception for autonomous vehicles. Big fan of cheesecake, corgis, and Disneyland.

Recent posts:

AI has an accessibility problem: What devs can do about it

AI has an accessibility problem: What devs can do about it

As a frontend developer, I use AI generously in my daily workflow. Not only does it increase my efficiency at […]

Jemima Abu
Oct 15, 2025 ⋅ 10 min read

Want to run your AI model locally? Here’s what you should know

Cloud AI made scaling easy, but local AI brings control, cost stability, and data privacy. Explore the hardware realities, tradeoffs, and strategies shaping this shift.

Clara Ekekenta
Oct 15, 2025 ⋅ 6 min read

Stop writing REST APIs from scratch in 2025

Writing REST APIs by hand is a thing of the past. Frameworks like tRPC, Fastify, and Hono eliminate boilerplate with schema-driven design, improving speed and safety.

Ikeh Akinyemi
Oct 14, 2025 ⋅ 3 min read
good dx is not enough component libraries featured image

Good DX isn’t enough: Why your component library still fails your team

Great developer experience feels amazing, until your design system starts breaking down. Here’s why good DX isn’t enough and what makes teams scale successfully.

Peter Aideloje
Oct 14, 2025 ⋅ 9 min read
View all posts

3 Replies to "When to use HTML5’s canvas"

    1. Hey Tom, we’d like to support canvas someday, but no solid plans yet for when that might happen.

      If you really need to capture canvas with LogRocket, you can render it to an image and put it under the canvas, which would be hidden from the user but recorded by LogRocket.

      At any rate, we cover a lot of stuff LogRocket doesn’t support because it’s still useful info for the community. Thanks for reading

Leave a Reply