Post

subtweet: rendering code efficiently in a browser is a nightmare and you will likely need some javascript to keep it performant. diffs.com is the best-in-class, open source library that does this.

if you want to be *really* snappy, you’ll need to give up the browser’s native search functionality. this is the cost of virtualization, which you’ll need in order to render only ~100 dom nodes at a time.

it’d be really nice to point the browser’s search against a buffer backing a virtualized view! alas! you cannot.

also, publishing a blog post putting the neighbor on blast after the same day they make an announcement is petty and makes the community look like it's subject to infighting (which tbf, it is...)

i’m sure you can figure out how i learned this, lmao

but what about lynx david

crates.io/crates/typos... docs.rs/crate/typos-... docs.rs/typos-dict/0... 😅

see tobias, the problem with javascript tends to be that it uses lots of CPU and *looks closer* oh. oh dear.

but yeah no let's keep being passive aggressive about it, that'll bring the project forward. I'm well versed in it anyway.