The logging engine was a strong selling point of IO Ninja since day one. To understand why it stands out, you have to think how most sniffers or monitors represent data.
Usually there is a "master list" of events, such as "incoming packet" or "error message", and then there is "details view". The user has to select the event in "master list" and then inspect event details in "details view".
The reason for this design of user interface is obvious: it's easy to implement. While this interface is acceptable, there are clearly situations when a single continuous log sheet (think of a huge HTML page) would be much easier to read.
So, why not use HTML? For a tiny log, that would have been fine. But unfortunately HTML is not suitable for displaying really huge pages, while logs of IO communications can grow to many gigabytes in size. So, we needed our own engine.
No other terminal emulator or packet analyzer can interleave binary data in text or hex-view forms with textual messages in potentially huge logs, providing a single, clean, searchable log sheet. IO Ninja could do it since the original release, and it got even better in version 3.