Probably because node imcompat / fresh start wasn't the only key differentiator for them?? Bun also had/has (in context of a leg up over node and similar to deno):

- typescript support - built in linting - built in package manager command - built in transpiler/bundler

Sandboxing and being more aligned with web standards, though admittedly on the latter I haven't checked back in on node with to see if there's been a push towards having the same tools as the browser engines instead of import('garys-crypto') etc

Nope.

https://xkcd.com/908/

It's a pain in the ass on new systems if it copied restrictive permissions to reset/gain access.

Ntfs equivalent of Chmod/chown is a "go have a long lunch" type of operation.

It's based off that 30% of code written by AI quote from the MS CEO last year.

https://www.cnbc.com/2025/04/29/satya-nadella-says-as-much-a...

Note that he said written by, not assisted; and also that there's been some major QA issues with win11 the last year, enough for Microsoft to have made a public apology/commitment to improve...

So, no definitive evidence, but the rest of the breadcrumbs provide enough to say that yes it does appear to have suffered from it.

Given the Debian policy seems more geared towards aided/assisted an existing dev than replacing them and shipping because the code works on the golden path on a devs monster pc ... Well I'd still keep an eye on it but trust OSS OS engineers to have some competence at knowing if this works and adjusting the policy later if it proved to be wrong.

Someone with financial / decision making weight their is going to ask why they are commoditizing models that run on "others" GPUs .... Since doing that makes their gpus less of the scarce resource..

It was unreliable post acq. and before the slop-tsunami, the latter has just multiplied the underlying issue of their ipv4 only half assed azure migration.

Yes yes yes, we know. Git is decentralised, you can just trivially push* anywhere!

* - the code. Just the code. only the code. Nothing but the code. You don't need the issues, the roadmap, the ACL of which human can do what, the API access keys for third parties, the artifact repos. Just. The. Code.

Somewhat arsey in my tone? Yeah. But having done two large scale (100+ repos) forge migrations of our company's client projects (SVN -> github, then later on github -> bitbucket) and seeing people completely ignore the metadata surrounding the code that isn't as easy to "just push" anywhere, somewhat justified.