Made the fan in my Windows 11 laptop spin up.

nurettin 18 hours ago | parent | next [-]

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.

▲

corysama 17 hours ago | parent [-]

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

▲

vunderba 17 hours ago | parent [-]

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

	▲	bschwindHN 14 hours ago \| parent \| next [-]
		We did something like that for a hiring project once: https://github.com/tonarino/acoustic_profiler
	▲	4k93n2 6 hours ago \| parent \| prev [-]
		vibe coding sounds "3.6 roentgen. not great, not terrible"

▲

OlaProis 13 hours ago | parent | prev [-]

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!

▲

WillAdams 9 hours ago | parent [-]

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.

	▲	OlaProis 3 hours ago \| parent [-]
		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.