[RIMR]

My first thought, as a network engineer, is that I already have access to pretty much every feature of this tool from the CLI. You ask if I would give that up for this app, and the answer is "not unless you integrate all the other CLI tools I use as features". Obviously, that's not reasonable, because my needs (like most engineers) are overly specific. You could never please everyone.

If this were an iPad/iPhone app, I would say that you nailed it, because this would be way easier and more complete than any of the tooling I have available on a mobile device right now. Otherwise, all of my other tooling is in the CLI, so I would ultimately be going out of my way to use this tool on my Mac.

The easiest fix I can think of is to open the door to third-party/community extensions so that people can add their own tooling to the app. You mention that this is largely a bunch of CLI wrappers, so it would be very helpful if we could write our own, and maybe even share them with each other.

[n1sni]

Understood. Trust me, I still keep a few consoles open... but it's a lot fewer tabs with NetViews going because for my use cases, it's doing 95+% of the work without effort.

I really like the extension idea... hmmm....