This is why I prefer clunky hardware with heating cpus and a slow disk. You can easily feel that you wrote bad code from audio and tactile feedback.

I’ve heard of people doing ambient performance profiling by instrumenting their code to insert clicks into an audio buffer based on a high precision clock and piping it out a speaker. You get to learn the sound of your code at 44.1KHz

This might be the most absurdly terrific thing I’ve read in a while - like a profiler equivalent of a Geiger counter.

We did something like that for a hiring project once:

https://github.com/tonarino/acoustic_profiler

*vibe coding sounds* "3.6 roentgen. not great, not terrible"

Which view/file caused this? v0.2.2 (coming soon) has significant performance optimizations for large files - deferred syntax highlighting, galley caching. If you can reproduce, please open an issue with details!

I launched the file, typed:

>Now is the time for all good men to come to the aid of their party. >test

and selected the last and made it bold using the formatting bar.

Thanks for the repro steps! This is helpful, formatting bar interaction shouldn't spin up the fan for such a small document. v0.2.2 has some performance improvements and is out, so it might be better, but this specific case might need investigation.