Post AdFO02OXHGR5r4BzX6 by lispm@moth.social
 (DIR) More posts by lispm@moth.social
 (DIR) Post #AdEeNqEPYXclBorxLc by galdor@emacs.ch
       2023-12-27T12:53:09Z
       
       1 likes, 2 repeats
       
       Funny how so many whine about SBCL executable cores. But with compression, my example program is 12MB even though it comes with a complete compiler. In comparison Go static binaries can easily grow beyond 100MB and I don't remember anyone complaining.Lots of #CommonLisp complaints are just a way to avoid saying "I don't like parentheses".
       
 (DIR) Post #AdFO02OXHGR5r4BzX6 by lispm@moth.social
       2023-12-27T21:24:12Z
       
       0 likes, 0 repeats
       
       @galdor #commonlisp #lisp that's not bad! I was experimenting with creating a command line #LispWorks app (Linux / ARM64). App starts empty at 8MB (no compression, but fully tree-shaken). Using AOC 2024 day 5 code (partially tree-shaken) gets me to 13MB. The executable is generated in ~ 1 second. Runtime is < 0.02 secs on an Apple M2 Pro CPU.
       
 (DIR) Post #AdGcZVC1n6tHp56gaW by lispi314@udongein.xyz
       2023-12-27T22:43:36.581192Z
       
       0 likes, 0 repeats
       
       @galdor @nytpu I'd recommend avoiding compression.It means you have to page the whole program in when first executing it. This wastes memory.If instead you just leave it uncompressed (or enable transparent compression at the filesystem level), you only page in those bits of the core which you actually need and the rest is left untouched.
       
 (DIR) Post #AdGcZW8AIxOYjOJ7Cq by galdor@emacs.ch
       2023-12-28T11:42:15Z
       
       0 likes, 0 repeats
       
       @lispi314 @nytpu Good to know. I was going to say that avoiding compression also means removing a runtime dependency on libzstd, but it seems SBCL always link it no matter what.