AutoHotkey Community

Mr.Chris has officially announced:



How do you guys feel?

EDIT: Poll closed on 11-Dec-2010 ( 2 Months from topic date )

I have mixed feelings about Chris' announcement. First, I think it's a great opportunity for _L to become mainstream (AHK v1.1 anyone?). OTOH I feel sad for Chris, as his entire post sounded like a defeat IMO. Not to mention vanilla is now called "AutoHotkey Basic"...

EDIT: 700th post. Time flies...

_________________
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]

Incorrectly named!.. Sounds like a derivative of 'Basic' language.
'AutoHotkey Classic' is the way to go, like when Pentium II arrived, the original Pentium was referred to as 'Pentium classic'



Congratz!

Where Chris has stopped, Lexikos and community are now continuing. I prefer AutoHotkey_L - unicode. It's the great upgrade of Chris' great work and it should become a mainstream. I recommend everyone to switch right now, but never forget Chris, his efforts and his great creation - AutoHotkey. Thank you Chris!

AHKC for now. until I might actually need arrays, unicode, #if and whatnot.

_________________
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 have to vote for "classic" simply because I use it 85% of the time.
I use C++ bins for multidimension arrs since forever, its just a force of habit.
TBH I've not had much need for native OOP, so, you know..

:lol: it does leave a sour taste in the mouth..

BTW whats up with L being 1st on the list on the download page?
Its almost like C is being bumped for 'newer and better'..

_________________
paradigm.shift:=(•_•)┌П┐RTFM||^.*∞

I vote AHK classic, but I waited an official announcement for to use other AHK version, let's go!

I have been tempted to use L but have never had the "need" for it.

One of the main things why i dont really change right away is because i have heard of incompatibility with Classic in some cases... can somebody clear that one out for me?

because if I can just use all my scripts once I move to L then there is no reason not to change. If they need change on the other hand then it would be wiser for me to wait until L becomes mainstream.

pretty much the same for me

Well, Chris hasn't been overly involved in the community since I started using AHK; therefore, it's not really a change for me. I am thankful, however, that Chris made an official announcement (he didn't need to), & that he put his "stamp of approval" - so to speak - on AutoHotkey_L.

I would like to say I'm thankful that Chris created such a great tool - & if his vision for AHK is complete, I'm thankful other users are skilled enough & willing enough to pick-up where Chris's work ends.

To my understanding, it's not so much that L itself is incompatible, but rather that Unicode is incompatible. A simple example is DllCalls - Unicode uses "W" & ANSI uses "A" in the MessageBox Function. For more details, see Script Compatibility.

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

I've looked at some of the extra features that AHK_L provides, but I don't have a need for any of them, so I am sticking with Classic for now.

David

_________________
With mixed feelings I am stepping down from all moderation responsibilities: http://www.autohotkey.com/forum/viewtopic.php?t=82906

I'm using AHKL for 7plus, it would've hardly been possible without #if and objects. I have not made the switch to Unicode and 64 bit yet, but will have to do so at a point.

For anything which is meant to be a bit more advanced in AHK this is the way to go right now.

Vote: Classic

I agree on naming it to Classic would be better than Basic.

I am using Classic for now, but have an eye keeping on Lexikos derivative. Really great what Lexikos and the others have made (at the beginning we had different variants and builds from different peoples). There was just one time when I needed Unicode really. But I agree that L makes many things easier to develop and it is even more fun.

The reason why I do not change to L are:

1. because I gave up Windows as primary OS. I just play with Ahk now and do not need it for productive usage. (So I am lazy on upgrading and learning the new things, to make use and understand L)
2. I am waiting for IronAhk to be completed. Then I switch to that variant as default Ahk.
3. Ahk_L means to me more a "wish, develop it and see what happens" (under heavy development and alpha phase), against the moral to be stable and future proof and reliable. Also its slower than Classic, in most simple benchmarks I did.

If L becomes more mainstream, then I change to it too as default Ahk on any Windows I use.

_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--

21 votes?

Friends, give me a direction.. I find it hard to write compatible code that will work with both versions. I want to stick with either of one: ANSI or UNICODE

So, please VOTE.

You can easily write code compatible with ANSI and Unicode, no need to write for a specific build.
Additionally I'm writing a tutorial on how to port scripts to AutoHotkey_L.

_________________
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]