News for hackers. Stuff that matters.
Re:Mem Is Shutting Down by kepano on Tuesday November 17, 2026 @10:11AM (#50532450)
What parts of Obsidian are slow? I am genuinely curious because I have been relentlessly working for years to make every interaction under 0.1s (and often much faster). To me every millisecond counts:

https://x.com/kepano/status/2004008730720194759

The app launches faster than OS animations take to complete:

https://x.com/kepano/status/2121695483781587269

https://x.com/kepano/status/2097412004734808471

Opening files and searching are instantaneous:

https://x.com/kepano/status/1900971833677279611

https://x.com/obsdmd/status/1960356539895558290

I wrote Pele to replace Mermaid and make it 100-500 times faster to render:

https://x.com/kepano/status/2111472054293913749

(apologies for the X links, these are also on Bluesky, Mastodon, and Threads if you prefer)

Re:Mem Is Shutting Down by archargelod on Tuesday November 17, 2026 @10:03PM (#50541332)
I did a simple human benchmark with currently latest appimage (extracted, to be closer to native experience).

first startup: ~1.5s - faster than I expected, but still slow

then I start spamming "new note" button - it takes around 40 new notes when it starts lagging, throwing "file already exists" errors and creating like 1 note per second.

was I clicking faster than a file system can respond - no. so what is taking it so long to process one of a simplest operation in the whole app?

okay, let's check ram consumption - 400MB - it is completely unreasonable for a note-taking app to take 10% of precious ram on my PC

And this is out-the-box clean, no cruft, no plugins experience. I can't imagine how bad it gets further on.

I understand that the problem is not implementation, but the core concept of using a web-browser interface for a note-taking app written in javascript. No, that doesn't excuse it being bad.