Wireshark seems a bit misleading. More like a "network inspector" if one leans towards the browser's network tab in the inspector?
But it really looks useful and I'll definitely play with it to see if I put it into my toolbox.
But it really looks useful and I'll definitely play with it to see if I put it into my toolbox.
re the Wireshark analogy: the reason I used that was because: (1) Subtrace operates at roughly the same level in the operating system stack, (2) has similar capabilities, (3) has an overlap in use-cases, and (4) has been the most effective at communicating what Subtrace is in my experience so far. I can see why the analogy is not a perfect 1:1 mapping (obligatory xkcd: https://xkcd.com/624), but naming things is hard and taglines are just names in idea space :)
Reading the documentation makes it sound like this sits one or two levels above where Wireshark usually operates, which is why I think the analogy is tough.
I'm saying this just FYI. I haven't actually looked at what your product does, but if it were to matter to me, it'd be based on what it can offer that Wireshark can't, rather than how similar it is to Wireshark.
and People who don't know how to use Wireshark want probably a better motivation to use Subtrace than 'its like wireshark' because there is a reason why they don't use it.
IMO the real UX problem is that there’s nothing in between “Wireshark” and “DevTools.”
What would be cool is a program that renders the real DevTools UI from a .pcap file (or stdin).
There’s a lot of use cases where I can capture all the traffic with Wireshark but I just want a basic DevTools interface.