Tokens are a staple in many roleplaying games. Miniatures are great, but expensive, and it limits your creativity to what you have in your collection. You can certainly buy a large collection of printed tokens fairly cheaply. But if you’d prefer to truly make your game your own, you need to make your own.

Most of the bytes associated with a webpage are images. A site that has a lot of small elements in separate files requires a lot of separate requests. And for small elements, a significant portion of that traffic is overhead.
I have built a Windows application to combine images into a single file and output CSS to use it.
My wife bought three strands of lights on clearance last year in anticipation of decorating the outside of our house for the first time this year. Big multi-colored C9 bulbs with dangling white icicle strands of T1 bulbs. It didn’t occur to me that they wouldn’t reach around the roof, turns out they had a total of 10’ lighted feet each, and nobody carried those strands anymore. It was time to hit Google and learn about my options.
In a world where CLR and JIT are generating native code for our desktop apps on the fly and horribly inefficient interpreted languages are serving our web content, both server-side and client-side, Intel and AMD folks must think our cheese slipped off our crackers.
The final verdict: SSE2 is the best option. It offers performance between 150% and 388% of the CRT strlen function. 32-bit CRT and libc strlen are quite slow and the 64-bit strlens are about twice as fast.