Era wrote:And if they do encapsulation, you can't even see the code to know what the h is going on!
...
Functions are not encapsulated, thus the code is visible, readable, modifiable.
The average AutoHotkey user relies on numerous functions without ever reading or modifying the code inside those functions. Some of those aren't even built-in, but functions posted on the forum. You don't need to "see the code to know what the h is going on" if the function or object holds to its contract.
Anyway, OOP mostly serves purposes unrelated to personal, individual coding. It's at base a clerical system, an effort at version control when people program in groups. Plus its theoretical abstractions appeal to academics and its complexity creates job protection via obscurantism.
Certain aspects of OOP (i.e. the ones that I've implemented) have clear value to me as an individual developer, so your argument falls flat from my perspective.
This isn't my job and I code alone 99% of the time, so I'll just accept what you (and others) say about benefits to group programming and "job protection". If OOP is for groups and academic types, let groups and academic types have it; everyone else may benefit from what they produce.
I'm not interested in theoretical arguments for or against OOP in general. I am more interested in feedback that has some direct real-world application, such as what changes in v2 make the program harder to use, or what changes could make it easier to use.