One concern is performance. Traces tend to be long, and running pythonEvery event gets its own ID. The plugin registers a callback to that ID.
code on each line will be slow.
If trace-cmd integrates a pager and a search mechanism that looks at the
binary data instead of the text, we could format only the lines that are
displayed. But that is going to be a lot of work and I don't think it's
worth the effort.
When the ID is hit, the plugin is executed on that event to display its
binary format.
This is done after the data has been saved in binary format to a file.
It may slow down the executing of reading a data file, but it does not
affect the running of the trace one bit.