看看Google关于autoit和ahk的趋势！
谷歌趋势，看起来学autoit比ahk的人多呢但是 Au3 更新太過緩慢了 回复 2# rchockxm
一则是autoit现在差不多该有的已经有了
更重要的是因为autoit现在闭源了，不是DevER得不到核心源码，也就谈不到提交Patches了，肯定发展慢了，不象ahk是开源的，是个热心的用户都可以提交一个patch上去：众人捡柴为焰高呀 听说ANK抄袭AU3 an AutoIt / AutoHotkey comparison
* AutoIt was first released in 1999. AutoHotkey forked from AutoIt in November 2003 because AutoIt at the time didn't have the ability to have hotkeys, Chris wanted them, and Jon thought it might not be an important feature. Some time after the fork, AutoIt went closed-source.
* AutoHotkey is thought to have less memory overhead than AutoIt. While I don't know of any thorough examinations that back this claim up, AutoIt/AutoHotkey do mirror the Opera/Firefox relationship somewhat (in that Opera tries to be trimmed-down and fast, while Firefox tries to be able to do everything under the sun, especially by having a large percentage of its functionality being implemented within its scripting-language, rather than in C-code).
o after installing AutoIt3, look in its Include\ directory... there's 70,000 lines of community-generated code there
o Firefox is similar.... there's lots of Javascript code that can be (mis)used in various ways
* AutoHotkey is open-source (GPL). AutoIt defies simple classification. Essentially, key parts will always be closed-source to retain control over the project, but the maintainers definitely go out of their way to foster a community of developers.
o AutoIt was originally GPL, and was GPL at the time that AutoHotkey forked, but closed its C source due to tensions related to the forking.
o The last version of AutoIt that was GPL is still available (see autoit-v3.1.0-src.exe here. Note that none of the files labelled autoit-docs-... are core C source). Even after this version though, some developers were able to submit patches based on the old code (though, of course, they had to be upmerged, which grows ever more difficult as time passes, so that's probably not possible now)
o There are a number of ways that AutoIt can be extended or contributed to. Since these allow third-party devs to accomplish most (but not all) of what they might want to do, AutoIt maintainers are less likely to want to go back to open-source.
+ the Include\ directory (called UDF's, user defined functions) is large and has all the source code visible, and the community can make updates to them
+ AutoItX is the AutoIt engine inside an ActiveX wrapper, allowing the functionality to be embedded inside other's programs. It has even allowed MoveIt to be created, which allows Lua scripts to be used instead of AutoIt's scripting language.
+ nascent plugins allow third-party C code to be called from a nice AutoIt-script interface
+ there are a lot of developers credited with contributing to AutoIt, but the process of joining the development team is potentially a long one
o It's not clear what the license the UDF code is available under, since all the code is visible, and many individual users contributed to them. If the license on those isn't explicitely stated somewhere though, it would default to the project-wide license, which says that it's standard copyright controlled by the core dev team.
* Various objective (but imperfect) metrics give mixed indications about whether one is more popular, though those backing AutoIt are probably better trusted on the whole than those backing AutoHotkey.
o metrics that indicate AutoIt is more popular
+ registered forum members (28k vs 8k, though this is lifetime-cummulative, and not indicative even of popularity over the last year)
+ Google Trends
+ Alexa (very flawed)
o metrics that indicate AutoHotkey is more popular
+ Yahoo backlinks (40k vs 30k)
+ quantcast rank (130k vs 300k) (probably even less accurate than Alexa) 但是 Au3 更新太過緩慢了 是啊，我不否认autoit能做不少事情，而且绝大部分事情我还不会做
但是，能不能，请它把脚步放快一点 呼吁开源啊，大势所趋 到底autohotkey怎么样呢，想试试了，呵呵 到底autohotkey怎么样呢 autohotkey与autoit有很大的渊源，呵呵 原是一家子，兄弟分家了 不是兄弟,而是父子。
现在要想看au3的基础函数源码都可以去看AHK相应的 回复 7# bakefish
慢的时候不会做, 快了就会做了吗?这是什么逻辑? aau 不错 开源
页:
[1]
2