premchai21

{ I can assure you that for some of us the response is both (a) more akin to amusement than to contempt and (b) hard to translate accurately. Adjusting for the frequent use of the word “human” to metonymically mean “sapience” is trivial. Adjusting for casual conflation near those concepts is easy in most discursive domains. Adjusting for some mysterious «nonlinear» behavior near «poles» is a chore but doable. Adjusting for things like transitively requisite, highly specific background emotions—well, extroversionism and kith are just the tip of the iceberg. “humans.txt” is peanuts. }

An interesting aspect of StartSSL is that they require physical residence addresses for natural persons even for their low-verification certificates. This seems a bit strong for “validate that the site that I'm talking to is ‘legitimately’ bound to name X”; this is the reason I've been on the fence about going that route.

Those are modified (apparently new-style) Spivak pronouns for gender-neutral singular third-person usage: https://secure.wikimedia.org/wikipedia/en/wiki/Spivak_pronou...

This also happens with "submit" after any entry whatsoever if there's no JavaScript around. Basic search forms should ideally not require such things.

Those of you of a more "hackable machine" bent may find Boodler (http://boodler.org/) interesting to play with as a soundscape generator. I can't comment on how it compares to this Flash app, since I don't have Flash on this machine; I'd be interested to hear such a comparison from someone who's tried both.

I find keeping the semantics of puts in my working memory to be harmful. The problem is that whereas (for instance) printf(...) is essentially an abbreviation for fprintf(stdout, ...), puts adds a newline whereas fputs does _not_. This is a headache to keep track of.

The result of this is that I always use fputs to write a plain C string to a stdio handle, specifying stdout explicitly and adding newlines if needed, and I ignore puts entirely, much like I ignore gets. The convenience is not worth the subtle error-causing asymmetry and associated mnemonic pain, especially if that code may ever have to write somewhere other than stdout.