logo

Changelog 40: Thank you ❤️ 🛹

Thank for the reaction to our new landing page, reply to get some swag. We also made some performance improvements, added new UX for print statements discoverability and published a video with Basement Studio on how we built the site.
profile photo
Jason Laster
Image without caption
Thank you for the incredible reaction to BugSlayer, our new landing page. It was humbling to hear how Replay has helped so many folks.
When we started, we believed that time-travel debugging could help people see their software in new ways. It is another thing entirely to hear it from all of you.
If you’d like to celebrate this moment, reply to this email and we’ll send you some sweet Overboard swag. Together, we’ll launch time-travel debugging to the moon 🛹 🚀
Image without caption

Performance

This past week we focused on all things editor performance. Stepping is now 5X faster. Scrolling and hovering in a large file is somewhere between 10 and 100X faster.
On the backend, we removed a slow code path that in one extreme case, brought a 1 minute 40 second start time down to 42 seconds. We found this path by using our open telemetry spans to start v8-profiler traces. This helped us see that the symbolify function which was demangling C++ call stacks coming back from the browsers was taking an excessively long time.

New User Experience

We’re also revisiting our new user experience so that print statements are more discoverable and it is clearer that they are editable. Next time you add a print statement you’ll see that the panel input box is more prominent.
Image without caption

Replay story

This week, we thought it would be fun to share how BugSlayer was built. Here’s a loom and replay. Under the hood, BugSlayer is built with Next.js, React functional components, and a lot of GSAP for animations. Huge props to the incredible team at Basement Studio for pulling it off.
Related posts
We share our plans on helping AIs resolve issues fully automatically
Over the past couple of years, JS frameworks like Next.js and Remix have gone full stack. We believe it’s time for DevTools to join the party!
We discuss a project for automatically fixing test failures
Powered by Notaku