strings

Strings are a good example of this: short strings can be tagged pointers, and long strings can be dynamically allocated.

For slug issues, Laravel comes with a support strings helper function for turning strings into slugs.

As for the set of strings, just assume it's every string possible, so 256^8 strings for an 8 byte password.

Also, for tiny strings (the only strings that this supports) on modern hardware, I'm not sure that O(n) takes much longer than that O(1).

They do things like take buffer size and then will truncate strings and leave off the terminating zero.

Early on this usually isn't a problem because some things just don't make sense like adding numbers and strings.

Then there is the fact that strings are no more in Python 3, but they are Unicode.

Again for average strings that's not really a problem, but when you start using bytes, special characters, et cetera.

Looks like all the font strings are images (makes sense, most of those aren't web fonts).

Because they're just C strings, you can print a selector by casting it to char *.

Fewer allocations, fewer pointer indirections, and some operations (like equality checking) become O(1) instead of O(n) for these tiny strings.

It's not NSString, but it's interesting to note that Objective-C selectors are just interned strings.

The spec talks about the server being "willing" to respond to requests from different origins, and explicitly mentions that it may support multiple origins ( "This is why the server has to send these strings: to confirm which origins and URLs the server is willing to service" ).