Yays You might as well make the program selection menu graphscreen and small font while you're at it :]

I think it would be amazing if you could have a thing in the options menu that would say something like Auto-Execute. That would execute your program under whichever shell you compiled it under right after compiling it. Its just an idea

That would be great for testing. However, there are problems: a lot of pepole don't use shells (so that would be impossible) and another lot of people compile for Ion for compatibility reasons, but I don't think people still use Ion (except that one guy I met at school )
Moreover, that would be a very heavy feature.

A random access array is too complicated to implement and wouldn't be as efficient as accessing native Axe data so I don't think you will see that soon unless I have some new revelation.  However, an expandable table of fixed size objects that only needs iterative access you will see in the near future because this is both simpler to program and can be made equally or more efficient than current native methods.  I also feel that out of all the data structures, this is used the most by Axe programmers.

EDIT: In the future if I support macros, writing your own array accessing like your example would be pretty simple.

I can't elaborate much because I don't know the exact specifications for it yet since its still in planning stages.  But basically a table is a data structure with objects.  There will be a special iterator loop structure, probably something similar in syntax to "For([A])".  You can add, remove, access, and modify only the current object from the iteration.  Order cannot matter during the iteration because the positions might change around during these operations.  You can access the Nth data byte of your custom objects, but you cannot access the Nth object because this would be unstable during the above operations and it requires a multiply.

This is all speculation so far.  I might also have to introduce the concept of "binders" to make this nestable.

You can change it as much as you want.  It just has to be read in order, not arbitrarily.  Enforcing this leads to HUGE optimizations in size and speed, plus it makes coding clean and compact.  If you need to access an X,Y pair you should be using a 2d array structure instead.  What this is more similar to is an object List (java), Table (SQL), or Vector (C++).

In the poll, what is meant by "Better UI Features"?

idk if it's possible or not, but can you add a "hittest" for object-object(sprites)?

Maybe auto-backup for libraries.