you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 4 months ago* (last edited 4 months ago) (10 children)

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.

  • source
  • parent
  • hideshow 10 child comments
  • [–] 6 points 4 months ago (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 6 points 4 months ago (2 children)

    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

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 4 months ago (1 child)

    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 :/

  • source
  • parent
  • hideshow 1 child comment