I'm a self-taught early-career generalist with professional experience at AWS working on massive scale high reliability backend services. I'm most at home working with web technologies, looking for a fullstack role. Especially interested in novel efforts in the realm of human/computer interaction. 2 years experience.
Fentanyl is active in a range very similar to LSD, it's the biggest concern.
25i-NBOMe is a drug similar in effect to LSD, but with a somewhat worse track record for safety. It's not likely to harm you, and unless you're fairly familiar with LSD, you might not notice the difference, but it has caused deaths due to severe vasoconstriction, which hasn't happened with LSD, even though many more people have used the latter. It's requires larger doses than LSD does, but it's still active at doses well under a milligram, and is usually sold on blotter paper just like LSD is.
Strychnine is also active in the LSD dose range. There was definitely some propaganda about strychnine-tainted LSD in the 70s, so it's hard to know if this has ever happened, or if it's just urban legend. But it's chemically plausible.
Fortunately, you don't have to just pray that your blotter doesn't have fentanyl in it. You can buy chemical test kits on the clear market and rule out all the culprits that should be cause for concern, and test that your blotter contains LSD (or at least a compound containing an indole group...). See https://www.reddit.com/r/ReagentTesting/ for links to vendors and more information.
Very unlikely that this has performance that competes with Sony and Microsoft. This is an integrated GPU on a battery-powered device with limited thermal regulation. The PS4 and Xbox One are always plugged in to AC and have plenty of space for a proper cooling system.
That's OK, this time the console actually takes advantage of weaker performance to offer a better form-factor. Whether that tradeoff satisfies consumers is yet to be seen.
I won't comment much on most of those points (they're not my style), but as for the last point you made about long identifiers and namespacing, I used to agree that that was a problem, but now I've changed my position.
If you choose a long prefix to disambiguate your library functions, then it gets annoying, but you don't have to use long prefixes. "sdl" and "ao" and "X" and "gtk" are great examples of short vendor prefixes for identifiers. In Go, since you brought it up, you have to reference identifiers from foreign packages with a prefix anyway. Go does let you change the prefix if it would otherwise conflict with your code, but because of syntactical concerns, it's more likely to conflict in the first place.
Which brings me to the interesting thing about C's lack of namespacing: it means that global identifiers look the same everywhere. This enables you to safely use grep and sed on global identifiers. It's not 100% foolproof because you can shadow a global with a local, and the identifier could appear in a string or comment, but if you're disciplined with the naming conventions of your globals, it should be very unlikely that a local accidentally shadows a global, and if a global identifier's name appears in a string, or especially in a comment, it's probably actually refering to that identifier.
This means that a language design decision turns simple refactoring features from a somewhat complex tool that needs compiler integration into "just use sed".
The point is that this informs the compiler of that behavior of free so that it can optimize it away. Basically it gives you some of the advantages you'd get if free were a compiler intrinsic (which it might be, idk).
Location: Washington, DC metro area
Remote: Strongly preferred for the time being
Willing to relocate: yes
Technologies: Javascript/Typescript/React/HTML/CSS, Java, MySQL, Python, C, Go, Linux, Docker, Node.js
Resume: https://www.linkedin.com/in/adrusi (formal resume available upon request)
Email: adrian 🅐🅣 adrusi 🅓🅞🅣 com