kupiakos

It's being used correctly: something that is conspicuously old-fashioned for its environment is an anachronism. A toolchain that only supports native builds fits.

> most mass shootings have occurred at locations that specifically disallow firearms, making them "soft targets" where the cowardly attacke

Most places with large crowds disallow firearms, and most mass shootings occur at places with crowds. You're confusing correlation with causation.

This is wrong. Steam lets you choose a Proton (Wine) version per-game.

Fixed prefixes also make a codebase significantly more grep-able. Want to find the definition of the function named `foobar`? Search `fn foobar` and that will always match, no regex required.

"comparable" was interpreted to mean "similar risk profiles", which is not true.

We don't have a recent smallpox outbreak to compare to for mortality with modern medical treatment. It's possible smallpox is only 5% deadly these days, we just don't know.

Comparing modern death rates to the 1919 flu, and to historical smallpox infection, is not useful. Medical technology has come a long way in a century and so average mortality rates have dropped for all diseases.

2019 and 2020 had particularly dangerous flu seasons and were still significantly less deadly than COVID.

Everything in modern society is scientist-caused if you go deep enough.

COVID is not comparable to the flu. It's 3-20x as deadly depending on a variety of factors.

Smallpox would still be significantly more deadly than COVID individually, but I'd bet people would take lockdowns much more seriously for smallpox than they did for COVID, preventing a pandemic and resulting in fewer deaths overall. Especially because people believe falsehoods like "COVID is comparable to the flu" because it downplays the risk.

It largely depends on the definition of "class" you're using. You'll raise some eyebrows calling structs that can't support implementation inheritance "classes".

You can also have implement different associated functions based on properties of generic arguments, which is quite different in design from just attaching methods to a struct.

I imagine that would likely fall under a new trademark or fraud law rather than copyright.

In the present participle, it's "shutting down", not "shutdowning". Or, "she shuts down the computer", not "she shutdowns the computer". "shutdown" is a verb as much as "alot" is a word. It's just a common typo.

I'm unsure what you mean - they said that there should be a space there and Merriam-Webster seems to support that. They put "shut down" and "shutdown" in the same page, and state that the verb version is "shut down". In the "First Known Use" section, it looks like it's just going with what the name of the whole page is.

The claim that requiring pronouns be based on assigned sex not being transphobic is akin to claiming Prop 8 wasn't homophobic. Judging that a e.g. a trans man cannot possibly be a man and use he/him pronouns is transphobic by definition. It sucks because the day of a trans person can be ruined by someone being an asshole and then feeling justified that they weren't "because biology".

Because the reality is, I'm trans and I don't feel safe participating on Hacker News anymore. If I try to ask someone to be respectful towards me, I know I'll be attacked because this is the top comment. And that sucks.

I'd absolutely love a way to display pronouns next to a username when configured. It's not required to follow the rules though. It's actually pretty simple: use they/them unless you find out otherwise. You're not required to seek out someone's pronouns.

As a trans person, it feels impolite (well, insulting) to refer to people as the _wrong_ gender. I don't see it as impolite to avoid gendered language in the case of not knowing one's gender, and only impolite in the case of knowing one's gender if great lengths are taken to avoid gendering.