Future API considerations
The aim of this page is to keep track of API 'lessons learned' - things that we would like to make more consistent but can't due to preserving backward-compatibility. These can then help inform future APIs, for example if we develop new sub-packages to replace old ones.
The QTable class was introduced because table columns with units act like quantities most of the time but not always, and we wanted to have a table class where columns with units are actually quantities and act like that by default. In an ideal world, Table would now behave that way, but we didn't want to break existing scripts that relied on the existing Table behavior at the time.
If it was a list-like object, we would get things like iter for free. See discussion in #3805.
The position is expected as (x, y) and the size as (y, x). See #7414.