AutoHotkey Community

Perfectly agree !!!

To me the size is not really an issue, because everything around the .exe be it hard drives, RAM, CPU's, etc... keep getting bigger and faster. Trying to cram everything into the smallest size at the expense of performance is a waist of time.

I value the performance and CAPABILITY of AutoHotKey OVER its size. Keep making AutoHotKey BETTER and have size as a secondary consideration AFTER the "good stuff" is added.

You got my vote!

I love the simplicity of AH. In it's current form I could see the exe growing considerably without it being an issue. The ease with which you can deploy AH to a computer is really important. It really set's it apart from the competition.

Although IMO a 9% decrease in size is not worth a loss in performance, conditional compiling would be a significant improvement...

If you mean the ability to exclude the code for commands and features the script doesn't use, that would be ideal. However I think it would require very specialized knowledge -- something only people who've developed real compilers would tend to have. Even with the right knowledge, applying it to ahk2exe might be quite time-consuming.

I appreciate the suggestion. Maybe an expert will see it someday and volunteer some time.

EDIT: The 9% reduction mentioned at the top of this topic was done several months ago. This is because a series of benchmarks showed that the reduction could be achieved without sacrificing performance. This was achieved by compiling performance-sensitive parts of AutoHotkeySC.bin with "maximize speed", but compiling everything else with “minimize size”.

I use AutoHotkeySC.bin below:

and I delete all Resources in AutoHotkeySC.bin using Resource Hacker:


Then the size of compiled scripts reduced by 25 KB.Is this will caused different performance?

No.

_________________