Just chiming in here, but at least two of the generations of cards there are from ~2005-2008 and we old farts definitely bought (or convinced our parents to buy) things from Newegg at the time!
I’m not an expert in the bio/chem side or really anything to do with mushrooms/fungi, but some families of mushrooms have commonly associated toxins. None of the below should be considered advice or recommendation or relied on in any way.
Amanitas often have a deadly toxin known as Amatoxin, for example.
Some others are sometimes reclassified from toxic to “sort-of-toxic” or “unknown.”
Common mushrooms like Morels can have their toxins cooked out (throw out the cooking water!), while others like Amatoxins will persist.
Still others affect some people, but not others - and some toxins induce negative effects in the presence of other chemicals in the system, like Inky Caps and Alcohol - the combination of which can be deadly, or not, depending on a number of factors.
My understanding of the situation overall is: it’s complicated.
Spore prints can be a huge help in identifying also!
There are some mushrooms that have very few known lookalikes (varies by geo/region), which have a handful of strong identifying factors. Morels, oysters, and a few others come to mind, where if you can confidently confirm these factors, you can be reasonably sure that you’ve identified them correctly.
That said, people sometimes convince themselves of these factors, especially when they haven’t had much experience identifying them before.
I do know a number of members of the IMA that have been there longer than me, and don’t forage at all!
I'm a member of the Illinois Mycological Association, where we do occasional surveys accompanied by biologists. They frequently take back tens of items for DNA sequencing.
If you're out there looking at a mushroom and think you know what it is, but aren't exactly 100% confident - remember that researchers who dedicate their academic career to fungi are frequently stymied by things found in a 2 hour walk with a few handfuls of volunteers: it might not be what you expect!
Slices are structures that hold a pointer to the array, a length, and a capacity!
So, when you slice a slice, if you perform an array operation like “append” while there is existing capacity, it will use that array space for the new value.
When the sliced value is assigned to another variable, it’s not a pointer that’s copied, it’s a new slice value (with the old length). So, this new value thinks it has capacity to overwrite that last array value - and it does.
So, that also overwrites the other slice’s last value.
If you append again, though, you get a (new) expanded array. It’s easier to see with more variables as demonstrated here: https://go.dev/play/p/AZR5E5ALnLR
(Sorry for formatting issues in that link, on phone)
Hey, neat - clicked around a little bit! Bug report: the contact page had some comments related to an article that definitely weren't related to the contact page.
I’m anti-spam myself, but I wouldn’t draw that conclusion from this post. It’s a post that links to a blog post on the YC primary domain site (that is, their company site), and we are on a YC forum hosted on a subdomain of the parent YC domain.
I wouldn’t visit Reddit’s blog and interpret talk about their successes there as indicating that the entire forum(s?) exist for marketing the parent.
And although, the HN forum itself definitely is great marketing, I mean to say that not all the content is marketing for YC.
I also wouldn’t draw that conclusion if someone who worked at Reddit submitted the blog post to a subreddit and it got upvoted there.
Unless it was boosted here, it’s only on the front page because of others voting it up. It’s more likely that it’s the PG effect!
Those patches are unlikely to be officially supported, though. I really support this mode of monetization, because community/free users get something, well, free, while others get something more for a bit more. It’s [hopefully] sustainable for the engineers and team behind the product, too!
That’s an optimization that can be added later, with some nuance. IIRC Go had a similar situation for years; I remember setting GO_MAX_PROCS in my init() or main()!
WELL, considering the time delay in provisioning on Hetzner/OVH, maybe Equinix Metal would work better? But, if you're provisioning + maybe running some configuration, and speed is a concern, probably using Fly or Hetzner Cloud, etc. still makes sense.
They understood and accepted the risks in that case - as an acceptable trade-off, which is different from the introduction of chemicals or compounds that aren’t well understood.
My understanding is that those scenarios are the exception, and finding obscure contracts that have gone undiscovered isn’t really an untapped fount of free, missed, opportunity.
That said, aggregators like bonfire etc. can get you pretty far if that’s your strategy!
While that may be true if contractors/competitors for contracts were generally unaware of the contract until posting, that’s usually not the reality. A lot of government contracting advice from experienced contractors is that if you’re discovering it via a public source (i.e. the website) you’re too late.