This is a common misconception. People without academic affiliation (based on their email address) require someone to vouch for them before they can submit to arxiv. And papers submitted to arxiv (with or without affiliation) are reviewed, and many are rejected.
arXiv does not review everything pushed to the site.
It's very easy to get in. It's becoming a common target for grifters who will "publish" papers on arXiv because it looks formal to those who don't know any better.
>Peer review has never really been blind and I suspect PIs will reject papers from "outsiders" even if they are higher quality.
I'm a complete outsider (not even in academia at all) and just got a paper accepted in the top math biology journal [1]. But granted, it took literally years to write it up and get it through. I do really worry that without academic affiliation it is going to get harder and harder for outsiders as gates are necessarily kept more and more securely because of all the slop.
J.S. Mill's autobiography is a fascinating read. He spends quite a lot of it discussing his early childhood, explaining that in his opinion he was not particularly special, rather, it was his father who pushed him to all those accomplishments. His father sheltered him from other kids so he was not aware that his accomplishments were unusual!
"The main axiom we introduce [...] states that for any organism in any species, either the species contains at most finitely many descendants of that organism, or else the species contains at most finitely many non-descendants of that organism."
This subject always seems to get bogged down in discussions about ordered vs. unordered keys, which to me seems totally irrelevant. No-one seems to mention the glaring shortcoming which is that, since dictionary keys are required to be hashable, Python has the bizarre situation where dicts cannot be dict keys, as in...
{{'foo': 'bar'}: 1, {3:4, 5:6}: 7}
...and there is no reasonable builtin way to get around this!
You may ask: "Why on earth would you ever want a dictionary with dictionaries for its keys?"
More generally, sometimes you have an array, and for whatever reason, it is convenient to use its members as keys. Sometimes, the array in question happens to be an array of dicts. Bang, suddenly it's impossible to use said array's elements as keys! I'm not sure what infuriates me more: said impossibility, or the python community's collective attitude that "that never happens or is needed, therefore no frozendict for you"
> the glaring shortcoming which is that, since dictionary keys are required to be hashable, Python has the bizarre situation where dicts cannot be dict keys
There is nothing at all bizarre or unexpected about this. Mutable objects should not be expected to be valid keys for a hash-based mapping — because the entire point of that data structure is to look things up by a hash value that doesn't change, but mutating an object in general changes what its hash should be.
Besides which, looking things up in such a dictionary is awkward.
> More generally, sometimes you have an array, and for whatever reason, it is convenient to use its members as keys.
We call them lists, unless you're talking about e.g. Numpy arrays with a `dtype` of `object` or something. I can't think of ever being in the situation you describe, but if the point is that your keys are drawn from the list contents, you could just use the list index as a key. Or just store key-value tuples. It would help if you could point at an actual project where you encountered the problem.
Turning a dictionary into a tuple of tuples `((k1, v1), (k2, v2), ...)`; isn't that a reasonable way?
If you want to have hash map keys, you need to think about how to hash them and how to compare for equality, it's just that. There will be complications to that such as floats, which have a tricky notion of equality, or in Python mutable collections which don't want to be hashable.
>I have zero idea how to make small talk with people I haven't known for years.
Here's a trick, it sounds stupid but it works like magic.
Just talk about mundane things that are physically present. Mention the color of the wallpaper. Mention the painting on the wall. Talk about how noisy the room is, or about the food on the plate in front of you. Literally act like you're an image classifier tasked with outputting a text summary of the scene you find yourself in...
If you're the cerebral type like I am, you'll feel afraid these topics will bore the other person. But surprisingly, they don't, if the other person is neurotypical.
To me, the fact that a blog post would be used to train AI is a good thing. Hell yes I want my writing to inform the future zeitgeist! I guess it helps that the things I want to write about are novel things no-one has ever written about. I could see how AI would demoralize me if I were otherwise employed writing Generic Politics Blog #84773. But as someone who writes original unique content, I'm like, hell yes, the more readers the merrier, whether they be human or AI or some unholy combination!
Some of us are born with small frenula of the tongue (or we undergo tongue-tie surgery as kids) and can thus perform Khecari mudra without the traditional self-mutilation used by yoga-masters. https://en.wikipedia.org/wiki/Khecar%C4%AB_mudr%C4%81 This can be useful for cleaning tonsil stones or post-nasal drip, but of course you must do so discretely since people would consider that absolutely disgusting
If you want to read out loud for long stretches of time and you hate taking breaks to catch your breath: you can read out loud while inhaling too! (It feels and sounds super weird though so this isn't very useful in practice.)
And here's a party trick related to OP's super power. Pick a distant object and cross your eyes so as to see it double, preferably with the two doubles distant from each other (i.e., cross your eyes significantly). Then, alternately switch between staring at the left double, and the right double. If you do it right, it will look like your eyes are moving in a bizarre alien way.
Then copy that and paste it a bunch of times to make it multi-line.
Cross your eyes so that the WORD's overlap (all except the leftmost and rightmost). You now see two cursors instead of one. Position your two cursors anywhere you want and then insert a space in order to make the corresponding WORD (or ORDW or RDWO or ORDW) sink into the screen. (Or rise if you parallel-view.)
We used to do this in the computer labs back in 6th grade.
reply