Jump to content
Sign in to follow this  
DasBo

Code breaking changes in every new version...

Recommended Posts

DasBo

I have a serious question to the AutoIt developers: is it intended, that the usage of this language is limited to some quick & dirty windows automation and unattended installation scripts, written on the fly and never ever touched again? If so: Why do you even put your time and effort into extending and maintaining the vast set of included and user AutoIt functions?

From an AutoIt users perspective it is hard (if not impossible) to maintain complex AutoIt scripts or function libraries. Every new AutoIt version involves the risk of rendering older scripts useless because of script breaking changes. Taking only the latest Version 3.3.4.0: Can you imagine, how many AutoIt scripts have to be customized and how many code examples posted in the forums become rather useless, if core functions like OnAutoItStart() and InetGet() are changed or removed? How should one even know, which AutoIt version was used for a code snipplet? Match the date / time stamp from a forum post or an au3-File with the AutoIt version history? :D

Who wants to take the risk of develop AutoIt scripts more complex than some ten lines of code, if chances are good, they simply stop working after the next AutoIt update...

Share this post


Link to post
Share on other sites
James

I have a serious question to the AutoIt developers: is it intended, that the usage of this language is limited to some quick & dirty windows automation and unattended installation scripts, written on the fly and never ever touched again? If so: Why do you even put your time and effort into extending and maintaining the vast set of included and user AutoIt functions?

From an AutoIt users perspective it is hard (if not impossible) to maintain complex AutoIt scripts or function libraries. Every new AutoIt version involves the risk of rendering older scripts useless because of script breaking changes. Taking only the latest Version 3.3.4.0: Can you imagine, how many AutoIt scripts have to be customized and how many code examples posted in the forums become rather useless, if core functions like OnAutoItStart() and InetGet() are changed or removed? How should one even know, which AutoIt version was used for a code snipplet? Match the date / time stamp from a forum post or an au3-File with the AutoIt version history? :D

Who wants to take the risk of develop AutoIt scripts more complex than some ten lines of code, if chances are good, they simply stop working after the next AutoIt update...

Wow Posted Image just wow... The developers spend hours of their own time developing AutoIt. Fixing bugs, adding new features, all for absolutely free. The only reward they get is a whole community who cannot thank them enough.

AutoIt develops each time to be better as a whole language. They spend a lot of time deciding what should happen and take a lot of users opinions on things. Some times, it just makes more sense to rename or remove a function.

And your 100% correct. AutoIt is a tool for literally:

quick & dirty windows automation and unattended installation scripts, written on the fly and never ever touched again?

That's what it says on the box right? Let's see:

AutoIt is a freeware Windows automation language. It can be used to script most simple Windows-based tasks (great for PC rollouts or home automation).

Ahh yes, exactly.

Share this post


Link to post
Share on other sites
AdmiralAlkex

OH MY GOD!!

In one year two functions change a little bit and the world end for you. I would hate to be around you when you get new shoes.

"This shit is impossible to use! The shoe-laces are 2 mm longer than my previous!!!11!!1!!1"

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×