EDIT: sorry, didn't mean to one-up someone's article. Do read it for it's intended purpose: showing how much time gets wasted, and how much a dev can get frustr

EDIT: sorry, didn't mean to one-up someone's article. Do read it for it's intended purpose: showing how much time gets wasted, and how much a dev can get frustrated, by a bad API. That's a pretty crappy API, but far from the worst: HP Fortify. When I used it about four years ago, the code examples wouldn't even compile, let alone work. The documentation was often flat out wrong. IIRC, there was at least one method with a named parameter, and the spelling of the parameter name was wrong. But then when one went to go retrieve it, it would be spelled correctly. It had every scent of a project that was spec'ed at HP in colloquial English, then sent to some far-off land where English is at best a second language for folks and price per hour is more important than coding chops. The API referenced in the article is, I'm sure, annoying to work with. But as far as getting actual work done, I would wager a good sum of money that the Fortify API will block you far, far more often and for longer than the Windows Event Tracing API. And am I correct in seeing that the web page turned my scroll thumb fscking white to match the background? Safari on macOS Catalina.