I vividly remember turning it on late in a Sunderland vs. Newcastle match. I was in central Bogota, Colombia. Struggling for reception, knowing we'd gone 1-0 down early in the match, I can still hear the commentator: "and who would have thought, after going one-nil down at St. James' Park, Sunderland would be two-one up". I shouted out loud like a lunatic. We won the game.

I've strung wire coat-hangers from windows in Nigeria, Ukraine, and Macedonia all trying to improve reception so I could listen to a football match.

There's a romance there that internet streaming will never touch.

Logging lets you refine the level of printing and is designed to make sense in the long term. There are many technical differences (structured logging, MDC etc.) that I won't get into but they are important.

To me it's mostly about the way you write the logs vs. the way you write a print. A log tries to solve the generic problem so you can deal with it in production if the need arises by dynamically enabling logs. It solves the core issue of a potential problem. A print is a local bandaid. E.g. when print debugging one would write stuff like "f*ck 1 this was reached"... In logs you would write something sensible like "Subsystem X initialized with the following arguments %s". That's a very different concept.

I don't see how this supports the theory that this is all about revenue from Windows OEM licenses from forced hardware upgrades.