384
Ex-Microsoft engineer rebuilds Notepad in 2.5KB using nothing but stuff Windows already had
(www.windowslatest.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 04 Jul 2026
384 points (98.0% liked)
PC Master Race
22779 readers
507 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: especially when new beginners have questions.
founded 3 years ago
MODERATORS
Size on disk doesn't correlate to memory usage or load time. You can get a very small on disk size by compression, or downloading the main executable at runtime.
Even the linked libraries may not contribute anything, if they are already loaded and shared amongst other processes. There are so many factors and trade offs that you cant really make any assumptions based off just the executable size.
Sure. I wasn't thinking of something like .kkreiger. I assumed that a small simple text editor would use a similarly small amount of memory. Shocked it ballooned so big. Sorry can't read the article at the moment.
It does some of the tricks that .kkreiger uses, including compressing the binary.
And at least according to a few reports, it uses 500MB of ram:
https://github.com/PlummersSoftwareLLC/TinyRetroPad/issues/21
Simply building without Crinkler compression changes the file size to 11 kiB and RAM usage to 1.7 MB. That's almost double what Microsoft's old Notepad (at a file size of 250-350 kiB, including an uncompressed multi-size RGBA icon of around 100 kiB and localization) uses but not bad, and probably the version most people will prefer for practical use.
Oh my god thanks for these memories
demoscene & 64K intro
.kkrieger was so damn cool. Mad impressive what they managed.
The premise is probably if you can optimize the code to be small, you are probably also optimizing how it runs too. Rather then just bloat up everything
Once you start optimizing for one aspect, others become less important. In this case, they are doing a few hacks to get to 2.5kb, which do impact runtime performance. A few users report it using 500mb at runtime due to the compression :/
Well that sucks, although I assume that's way better than the AI bloated version that now comes with Windows.
Thinking it doesn't correlate at all seems foolish. There is some correlation, it's just miniscule.