AutoHotkey Community

Hi guys,

I've just posted an interview with Chris on DLS, about whether or not AutoHotkey is dead:

http://www.downloadsquad.com/2010/07/05 ... developer/

AutoHotkey is not dead... it's now developed by the community.

_________________
fincs
Highly recommended: AutoHotkey_L (see why) (all my code snippets require it)
Formal request to polyethene - I support the unity of the AutoHotkey community
Get SciTE4AutoHotkey v3.0.00 (Release Candidate)
[My project list]

Donateing is always an option.

_________________
rawr. be very afraid
*poke*
Note: My name is all lowercase for a reason.
"I think Bigfoot is blurry, that's the problem. It's not the photographer's fault, Bigfoot is blurry. So there's a large, out-of-focus monster roaming the countryside."

I'm happy to hear that Chris is still alive.


Not sure why you say it isn't happening. That's exactly what AutoHotkey_L is. I'd have no problem calling it a continuation of the main branch since there have been no parallel development (AHK_L is pretty much a superset of AHK). The only thing missing is to make it official (either by completely replacing AHK, or to at least have an installer and/or direct link from the Download page).

Thanks for interview, ezuk

In other words, AHK is dead, but may resurrect in the future.This is my problem with the AHK_x branches. They introduce features very few of us need in AHK (there are large and complex languages, which handle that much better, so we should use those languages for complicated things), but bugs in the core AHK are not fixed, inconsistencies, exceptions remain, and basic features like simple arrays or dynamic code execution are missing.

And what happens at the next Windows update, or the one after it? I already expressed my fears that then AHK might stop functioning properly, and our time and effort invested in developing scripts will turn out to be wasted. For a while I have only written very simple scripts for myself and for my family, and keep on searching for an alternative to AHK. AutoIt is not one.

I don't think the 'interview' is that useful to be honest. I like AutoHotkey the way it is just fine and have to agree with Laszlo, the only worry I have is that indeed that someday it might stop working - and there is no telling if any of the other branches will keep on working as well as they also have a limited number of developers. I don't understand any of the new features nor do I see a point in learning about them (for me that is). My 2cts.

_________________
AHK FAQ
TF : Text files & strings lib, TF Forum

Laszlo wrote

hope that autohotkey always works ..... would it very missing

[Removed quote-spam. ~jaco0646]

But anyway, ezuk, I appreciate you mentioning AutoHotkey & even writing scripts in it...but, I take great offense to the code in the image...


...I mean really?...(you are promoting AutoHotkey right?)...if AutoHotkey (capital A, capital H, lowercase k...except when initials only, then it's: AHK) is dead, you're supposed to switch to a completely different syntax (which is bad {too rigid/strict})...& then have to use a MEAN SUPPORT FORUM if you need help? If you even hint at having a problem on the AutoIt forums, you will be insulted (by admins/mods, no less)...& banned. Notice how I'm critical of the code chosen for the image, but didn't insult you/call you names.

Better code for that image would be...


...now that may be too-complex for an image, but I think right now, AutoHotkey_L is the choice for full-functionality & new features, but later when IronAHK is ready (version 1.0+) (1.0 is supposed to support 99% {or so} of current AutoHotkey syntax), that will probably be my choice, cuz it'll automatically be cross-platform & I believe compiled scripts will only contain the code they use (aka smaller .exes). I have not tested any of the AutoHotkey-spawn yet either, but I absolutely would try them OVER AutoIt any day!


...everyone always beats AutoHotkey down, cuz of the syntax. There may be PARTS of the syntax in the dark ages (just don't use them, if you can avoid it), but it's really possible to write nice code. I'd would like the syntax of AutoHotkey to be more JavaScript-like (not BASIC-like or really strict like AutoIt). I love JavaScript, but I've seen people commenting on how they hate JavaScript because of <this> or <that> when that exact thing is why I love JavaScript.


...I've been here since 2004 & I'm not sure HOW to help (yes, I read that topic in 2006). I really don't want to write a bunch of code & have it "rejected"...so, I've been waiting for a more official "dev team", but that hasn't happened. However, now, AutoHotkey is still Windows-only, so there might not be a point in starting now, I'd much rather develop/help a cross-platform AutoHotkey...but I hate the C# (C Pound) language, so I can't help with IronAHK...I'd like an IronAHK minus the Iron/.NET...maybe wxWidgets or Qt...

I am not belittling AutoIt, but I can script only the AHK way

SKAN, you do not know any other languages?

He speaks English too

_________________
AHK FAQ
TF : Text files & strings lib, TF Forum

No. Only AHK and Foxpro for DOS

I think I understand C++ and can learn it in a while, but do not have the patience to compile for every run.

Thanks for the interview. Interesting stuff. I wish Chris was still active in this project but what are you going to do?

...we're all going to go to his house, drag him back to his computer & MAKE him update AutoHotkey!!! (lol, jk, if I really need to say that...but) PLEASE COME BACK CHRIS!!!