News for hackers. Stuff that matters.

A comment on ZapFast: A fast, native WhatsApp client in Rust and egui. Parent comment

Re:ZapFast: A fast, native WhatsApp client in Rust and egui by andai on Sunday November 08, 2026 @05:33AM (#50412020)
Hello world in Rust is huge, and every actual program I've looked at installed dozens of packages for basic functionality.

Turns out all those zero cost abstractions add up to a lot!

[ Parent | on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by tcfhgj on Sunday November 08, 2026 @06:24AM (#50412323)
The number of packages doesn't have anything to do with this
[ Parent | on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by andai on Sunday November 08, 2026 @07:00AM (#50412517)
It does with the compile times lol

Is there actually a way to see a breakdown of memory usage for a program? If you want to see where all the memory is going?

[ Parent | on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by tcfhgj on Sunday November 08, 2026 @07:45AM (#50412792)
The topic was ran usage during runtime.
[ Parent | on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by andai on Sunday November 08, 2026 @10:01AM (#50413889)
What causes that?
[ Parent | on HN ]
Re:ZapFast: A fast, native WhatsApp client in Rust and egui by saghm on Sunday November 08, 2026 @09:44AM (#50413777)
> Is there actually a way to see a breakdown of memory usage for a program? If you want to see where all the memory is going?

Flame graphs are a pretty common tool for this (maybe slightly less common than using them for seeing the breakdown of the time spent when running).

[ Parent | on HN ]