Ability to put other columns before the name field

There are often times when an object is not identified by its name but its id or something similar. And it makes much more sense to put that field first in the table.

For example, this is the table view containing Leetcode problems, the name is secondary here, two names could be very similar, but its id would be unique.

Better behavior

One column could be moved left to the name column.

Future possibility of this approach

The moved column could be a checkbox, which would behave just like the task for that view

Or it could be a n-state checkbox/select which would also make sense.

This would also serve great with the collections 2.0 architecture (different context different behavior), like in one view (buy list) the task_done checkbox could be used as the task done status, in other view, the date could be used there like a journal?? this requires more thought though.

Final thoughts

But one thing this brings is ability for an object to be of normal page (nothing to the left of name), dated page (creation date to the left of name), task (checkbox to the left of name).