Suggestion: Should we call thisstats orinfo so as to not be confused withhttps://en.wikipedia.org/wiki/Stat_(system_call)?

@mafredri thestat name (by itself) is not great. I was trying to be consistent withdstat,vmstat,sysstat and friends. We could follow in the footsteps ofdstat and make itcstat? I worry thatinfo orstats could be confused for a command that gets the stats of a workspace. I'm also hesitant to use a long name because this invocation will be repeated frequently in templates.

@ammario fair. Given that, I don't really have any great suggestions or alternatives. Calling itsysstat would be quite good, but wouldn't want it to be confused with the actual suite of tools. Likewisecstat is good but doesn't inherently mean much to the casual user. I guess that leavesstat orcstat as options, or if you manage to come up with a better one 😄

@mafredri sysstat is my favorite as well. Might just steal the name.

This Pull Request is becoming stale. In order to minimize WIP, prevent merge conflicts and keep the tracker readable, I'm going close to this PR in 3 days if there isn't more activity.

I'm not going to have time to work on this in the next couple of weeks.@bpmct may assist in finding someone new.