Apparently, late last week was an event known as the Cricket Celebration Bowl.
I thought to myself, “The Cricket Celebration Bowl sounds like the name of the least popular item on the Panera menu.”
And no, it’s not a cricket match either.
Turns out it’s an American college football game between the champions of two collegiate leagues, named the Celebration Bowl, but sponsored by Cricket Wireless, making it the Cricket Celebration Bowl.
In 2017, Safeco Field, the local Seattle baseball stadium, included grasshoppers on the menu (sometimes popularly misidentified as crickets). In 2018, you could get actual crickets at the Oakland Coliseum (at the time, another baseball stadium).
Hi. Actually, I have something more IT-related in mind right now. Why don’t EXE files ever have spaces in their file names? Yes, NTFS allows it, but do compilers support it?
Execute dir /s “C:\* *.exe” and you may find that there are some executables with spaces in their filenames in your system. In mine there are like a dozen.
None of the compilers and interpreters I have worked with have problems with spaces, either in the filename or in the path, but you have to quote those paths. For that reason, the convention is for programs intended to be used from the command line to not have spaces. But that’s only a convention.