Ciri has a relationship with a woman in the books, so I’m not sure you will miss what I assume you’re referring to as “the masculine indulgences” as much as you think you will.

On the other hand, CDPR retconned a shedload of that book so we shall see.

… Is this a trick question? The object, provided by the library (net/http which is about as default as they come) sets “DefaultMaxIdleConnsPerHost” to 2. This is significant because if you finish a connection and you’ve got more than 2 idles, it slams that connection close. If you have a lot of simultaneous fast lived requests to the same IP (say a load balanced IP), your go programs will exhaust the ephemeral port list quickly. It’s one of the most common “gotchas” I see where Go programs work great in dev and blow themselves apart in prod.

https://dev.to/gkampitakis/http-connection-churn-in-go-34pl is a fairly decent write up.

Eh, I don’t know anyone who managed to get themselves to Cannabinoid hyperemesis syndrome without legalization. Easier access to high quality highly concentrated doses has been increasing prevalence.

If it’s the 1990 cosmic brownie, then yes. Modern day? Nah bro.

Are you supposed to be injecting pentobarbital subcutaneously? Pretty sure I remember it being administered as an IV

Yea, the vet tech pointing the sharp end of the murder drug at his hand while he injects… esh.

Any of the video game console companies.

And yet: You’ll still be limited to two simultaneous calls to your REST API because the default HTTP client was built in the dumbest way possible.