Order of arguments (for "drop", "take", etc.)

Nobody has claimed this yet.

Is there a reason why the order is drop(BasicList, ZZ) and not drop(ZZ, BasicList)? The most common use-case I have is to e.g. remove the last elements in a nested list, e.g. if
```
L = {{1,2},{1,0,3},{2,4},{3,5}}
```
then currently one has to write
```
apply(L, x -> drop(x, -1))
```
If the order were reversed, then one could take advantage of the subscripted syntax for functions with multiple arguments to instead write
```
L/drop_(-1)
```
This is actually a special case of a much more general feature request I have thought about, which is to have M2 accept arguments in any order as long as the arguments have all distinct types. I think even a naive implementation of this would greatly increase the user-friendliness, without inducing a noticeable performance hit (since functions only accept at most 4 arguments). Are there any drawbacks to this?

Start by reviewing the issue's examples for drop, take, apply, and subscripted syntax, then inspect how M2 currently handles argument order and multi-argument functions. Done requires an agreed scope for the general feature, including its drawbacks and implementation boundaries; no source files or tests are named in the issue.

Written by the indexing model from the issue text.