- In addition to how long the existing code has been running, it might be nice to show system uptime.
- It might also be cool if it told you what USB devices were connected, as well as if a connection exists over LAN. (The elephant in the room is obviously modules. Sadly, it's not possible to ID them automatically at this time.)
- Memory usage may not be that useful of a statistic, frankly. IIRC, the JS runtime will grab a bunch of memory at first, then climb steadily until it has allocated almost everything, and enter an endless cycle where it garbage collects down, climbs back to ~full usage, garbage collects down, etc.. Point being, it'll consistently be a high number, and one that likely won't be correlated with "how hard the Tessel is working" (or whatever it is the desired information is here).
As usual, I'd like to argue in favor of not shying away from jargon simply because it's possibly new to the user.
tessel ap makes sense if you know what it stands for, and if you don't, you should probably run
-h anyway to figure it out. I also see no reason we couldn't have the short and long form of the command (
I associate hotspots with coffee shops and airports (and always with access to the internet at large, which may not be the case here), and router is, in my mind, too ambiguous of a term.