4 ms·
Ask HN: What would you consider an acceptable size for a command-line utility?
I am looking to write a command-line utility - it will be domain-specific but somewhat similar to PNGOUT [1]. End-users (running Windows) will download an EXE file to use on their own systems.
Many languages are candidates to write such a utility, but one difference between them is the size of the generated EXEs:
C++: < 500KB
Lua: ~ 500KB
LuaJIT: ~ 1MB
Go: ~ 2MB
Python: ~ 4MB
JavaScript (V8): ~ 10MB
PyPy: ~ 40MB
(I have decided against using an EXE compressor such as UPX. Note that PNGOUT itself is only 38KB, in part because it has been compressed.)
Which (if any) of these sizes are sufficiently large that they might put you off downloading the tool? Or, from a developers point-of-view, might put your users off downloading?
[1] http://advsys.net/ken/utils.htm
- brudgers 10y agoTo me, optimizing on size seems premature. People use Excel to manage shopping lists. 40mb is not highly unusual for a web page...and the utility will probably have more utility than the typical (2mb) web page. If size is a huge factor, writing it in PowerShell and distributing the source would probably be the smallest easy way to approach a Windows command line utility. Good luck.