News for hackers. Stuff that matters.
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by fastball on Saturday November 07, 2026 @11:52PM (#50410506)
[delayed]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by codedokode on Sunday November 08, 2026 @12:05AM (#50410548)
To use memoization you must use immutable structures (otherwise React is unable to detect changes) which are a pain to use and are slow if not designed properly. Do not believe me, try designing for example an algorithm that accepts a huge immutable sorted list with keys, a large sorted list of bulk deletes/inserts and produces a new sorted list with minimum operations. I made 2 or 3 prototypes and they still are not good and not even working properly.

In my book, a good UI framework simply attaches to a mutable model made of arbitrary objects, detect changes and displays it with minimum number of operations. Doesn't require to use any proxies or immutable data or store data in components. Shouldn't be difficult. Why nobody made it, I do not understand.

Re:ZapFast: A fast, native WhatsApp client in Rust and egui by asdf88990 on Sunday November 08, 2026 @12:27AM (#50410656)
This is incorrect. You don’t need to use immutable structures to have stable references which is what matters.

Use context liberally instead of plumbing things through prop’s needlessly and you’re halfway there.

Re:ZapFast: A fast, native WhatsApp client in Rust and egui by rtpg on Sunday November 08, 2026 @02:40AM (#50411190)
React isn't immediate mode by my understanding.

In my head it's retained mode + the diffing layer, which sounds the same but if you try to write an "immediate-mode" API (say, using hooks) in React you'll find yourself churning a lot.

At least unless you use the magic React compiler that memo-izes everything correctly.