Not saying he wouldn't have banged on the button, for all he was worth, but no one in their right (or even severely sick) mind would ever let him near it.
Thompson: The man who invented gonzo journalism, writing beginning in the 1950s for numerous publications but most notably Rolling Stone, best known for Fear and Loathing in Las Vegas, serialised in RS, published as a book, and the basis of two films, Where the Buffalo Roam (loose adaptation, 1980) and more faithfully in 1998 under the original name, starring Johnny Depp and Benicio del Toro.
This is of course entirely expected. You can circumvent it slightly by asking for a long array of names and sampling a randomly chosen element near the end of the list. Say ask for 50 names and use the 41-50th element stochastically.
Not perfect, more expensive, but it helps a little. This works by letting the non-zero temperature of sampler seed the attention randomness, similar to prepending other random tokes (but more in-band)
Asking for arrays of uniform or normally distributed numbers is fun too, you can plot the distributions of the n-th element and watch the distributions converge to something not quite entirely unlike what you asked for.
Often there's some bias between element indices too, eg. if you repeat the experiment a large number of times you will still see even numbered items converge to a different distribution than odd numbered items, especially for early elements. Hence the stochastic averaging trick over the last few elements.
It's rendering visibly narrower than the big dash up thread for me, on FF on Android. (Maybe HN's stripping one or more of the combining chars though, so it's not actually showing what you meant in full?)
It isn't a special letter or symbol in arabic, it's just a regular sentence that was added to unicode since it both holds symbolic meaning in islam and is used often enough to be useful. Some fonts render it like any other arabic, making it look like one big sentence as a single character, but others render it as calligraphy
Huh. I've noticed CC running build or test steps piped into greps, to cull useless chatter. It did this all by itself, without my explicit instructions.
Also, I just restart when the context window starts filling up. Small focused changes work better anyway IMO than single god-prompts that try do do everything but eventually exceed context and capability...
Surely any distinguished connoisseur of terminology gatekeeping such as yourself is able to distinguish between 'cc' and 'CC'. My terminal is able to spot the difference, you should be able to as well.
CC is an environment variable / internal variable used by most build tools to identify the current C compiler. cc is the standardized name of the executable, now usually an alias for gcc.
Both CC and cc refer to the C compiler, in slightly different ways.
Assuming you already using object storage in your project, but don't use Redis yet it wouldn't be re-inventing but just avoiding an extra dependency that would only be used by a single feature.
on edit: liked the Garamond better, since the font is a bit thicker, checked it on "ſpake" and was obviously a long S whereas on the thinner Baskerville still looked like an f to me. Although the original text was perhaps too thick for me.
just noted that in reply to my post but repeat here:
yeah I was wrong, I happened to look back at Maiſter and my bad eyesight and the resolution made it look like the long s had a crossbar from the t next to it in the default font.
on edit: this was probably where my problem generally was, in lest and Maister and anything where the long s is next to a t it looks very like an f to me, although if I zoom to 170% then it is clear, however at that size it introduces its own reading problems; unfortunately my reading glasses are broken so I just struggled at a lower resolution.
yeah I was wrong, I happened to look back at Maiſter and my bad eyesight and the resolution made it look like the long s had a crossbar from the t next to it in the default font.
Curious how others here are reading this post.