Whenever something like this comes up, I always think back to the excellent paper, "The Structure and Legal Interpretation of Computer Programs." I don't have a specific answer, but I like to review this paper whenever a question like this is posed.
While there is overlap between vtuber communities and HN, the culture is quite different. When one does come up, it is eternally September on HN. In vtuber communities/culture, the persona of the vtuber is treated as entirely separate from the person behind it, even in cases where it's exceedingly obvious (e.g. someone leaves an agency to work independently).
At the very least, it is rude to disseminate, draw attention to, or even speculate aloud about the identity of the person behind the avatar. Typically it's considered harassment/doxxing (I believe this is because vtubing culture is largely derived from Japanese idol culture, which appears to be structured around dealing with stalkers). That is to say, "upholding the kayfabe" is a bare-minimum of respect.
I could see why people on the Asahi team considered HN to be a host of harassment, considering even a cursory search of HN turns up comments "compiling evidence" about Asahi Lina's identity (including one still-up comment that straight-up links to Kiwi Farms, which is almost certainly done for purpose of harassment). I'm not sure if Hacker News ought to be moderating comments that deconstructs pseudonyms where clear effort has been made to separate it from the person behind them, but I also empathize with not wanting to be linked to accordingly.
Investment is generally considered profit-seeking behavior (i.e. not rent-seeking). Building an apartment and renting it out is clearly profit-seeking behavior, but if you were continuing to rent it out doing the bare minimum to keep it from falling over 40 years later, that would be pretty clearly rent-seeking.
From this, we can conclude that there must be some point after an investment is made where continuing to benefit from it transitions to rent-seeking behavior.
I am well aware of what the phrase means, and I re-read the Wikipedia article to be sure. Maybe you read the use of the word in a different way than I did, but I helpfully included my precise interpretation of it in my comment to clarify the meaning.
> the term "rent seeking" has literally no place in a discussion about landlords
Having "literally no place" is certainly a strong choice of words, particularity as it was introduced in this thread as being a inaccurate label to apply to landlords.
Personally, I first learned about the term applying it to Feudalism, in which the (land)lords' only contribution was their ownership of the land. That example alone seems to pretty handily disprove your claim of "literally no place", in fact it's specifically cited in the Wikipedia article as the Georgist interpretation of economic rent.
The concept of "landlords do nothing while collecting passive income, therefore not creating any value but instead are just exploiting that they own the land" would be correctly described as "rent-seeking behavior".
Well, yes. I did say something to that effect. Blaming BSODs on invasive anti-cheat out of principle is a political position, not a scientific one.
> During the same time period when people were complaining about BSODs, I didn't experience one. I was running the same build of the game as them and playing on the same difficulty and sometimes recording it via OBS (just like they were). What I didn't have was a AM5 motherboard, I have and older AM4 motherboard which doesn't have these problems.
I understand what you're saying here, but anyone who does a substantial amount of systems programming could tell you that hardware-dependent behavior is evidence for a hardware problem, but does not necessarily rule out a software bug that only manifests on certain hardware. For example, newer hardware could expose a data race because one path is much faster. Alternatively, a subroutine implemented with new instructions could be incorrect.
Regardless, I don't doubt that this issue with Helldivers 2 was caused by (or at least surfaced by) certain hardware, but that does not change that given such an issue, I would presume the culprit is kernel anticheat until presented strong evidence to the contrary.
> So I am extremely sceptical of any claims of BSODs because of a game.
Generally speaking, I am too. That is unless there is kernel-level anticheat. In that case I believe it's fair to disregard all other epistemological processes and blame BSODs on the game out of principle
Dropping back here to say that I have been playing around with Monado + OpenComposite + WlxOverlay and while it's been plenty janky, it has actually usable performance when it works.
The splash page on that website seems to be primarily AI-generated images. It looks cheap to say the least - such an obvious corner cut it's hard to have confidence in the product.
That seems super far fetched given that 37%[1] of the world's population does not have internet access. You could reasonably restrict further to populations that speak languages that are even passably represented in LLMs.
Even disregarding that, if you're making <3000 euros a year, I really don't think you'd be willing or able to spend that much money to let your computer gaslight you.
Ironically, I'm considering installing Bazzite alongside NixOS because it's proven to be nearly impossible to run SteamVR properly with how Steam is packaged
From my perspective, not having to deal with strings is one of the big benefits, but I believe the main argument is actually that it trivializes alpha equivalence.
As for renaming, if you're going to be looking at every binding anyway, changing most of them is no big deal (unless of course that entails doing many deep copies)
I used De Bruijn indices when attempting to prove correctness of a toy language of mine. It's an elegant solution, but I found them exceedingly difficult to reason about both intuitively and in proofs. That being said, I've yet to find a better system (that isn't just augmenting De Bruijn indices) for implementing any sort of lambda calculus.
Lean is more complex to develop in than most programming languages since it relies heavily on interactive programming, i.e. the context pane. The "easy way" is with a plugin.
If you're interested in learning more about Lean for writing proofs, I would recommend The Mechanics of Proof [0]. It strips out a lot of the convenience tactics in Mathlib to focus on the more primitive mechanisms Mathlib builds on.
https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4445484