I generally agree with you that choosing something based on where it's hosted is dumb. I still think there could be an impact wrt a network effect.
The original comment you replied to was talking about "the loss of network effect" and you sounded dismissive of it. It might not even matter, but I think it's somewhat fair to say it could have an impact.
I agree. It's possible in the future a project hosted on codeberg is a silent "stamp of quality". Though, I still think there could be impact wrt a network effect.
“An Ad hominem refers to when a speaker attacks the character, motive, or some other attribute of the person making an argument rather than the substance of the argument itself”
It’s definitionally an ad hominem against Jared. If he stuck to why he thought it was bad for Bun to do this, I would be more sympathetic.
The answer seems to be yes [0]. Although I think it's important to state The Web Archive link proves that the recent Fable banning was not the catalyst for the page being linked.
Will Fable be back behind an ID verification step? I wouldn't be shocked if that happened. However, this specific support page and the ID veridiction process is not new. It is currently enforce.
It appears (but I can't be certain and don't think it's in bad faith) that many people are under the assumption that this is a result of the Fable banning. As a datapoint, I did some form of KYC verification to use OpenAI's cybersecurity platform a few weeks ago.
To be clear: I still think this is an important discussion.
>By far the most important aspect is that we need to keep the new codebase as compatible as possible, both in terms of semantics and in terms of code structure. We expect to maintain both codebases for quite some time going forward. Languages that allow for a structurally similar codebase offer a significant boon for anyone making code changes because we can easily port changes between the two codebases. In contrast, languages that require fundamental rethinking of memory management, mutation, data structuring, polymorphism, laziness, etc., might be a better fit for a ground-up rewrite, but we're undertaking this more as a port that maintains the existing behavior and critical optimizations we've built into the language. Idiomatic Go strongly resembles the existing coding patterns of the TypeScript codebase, which makes this porting effort much more tractable.
TLDR: Typescript -> Go is much easier than Typescript -> Rust/Zig/$OTHERNATIVELANG
This is a very interesting reference/jupyter NB/historiography someone put together about deciphering Khipu, the cord-based numbering system/ancient Excel from the Inca's.
"Welcome to The Khipu Field Guide - Travel back in time to the Inkan empire of the 14th through 16th century. Explore how the Inkas used cloth to communicate and record commitments. Journey with me, as I work with other khipu scholars, to decipher the enigma behind a knotted mop of camelid yarn."
There is some statistical analysis here but part of my hopes in posting on HN is perhaps someone here might get nerdsniped by it.
The original comment you replied to was talking about "the loss of network effect" and you sounded dismissive of it. It might not even matter, but I think it's somewhat fair to say it could have an impact.