HN user

oauea

1,501 karma
Posts0
Comments716
View on HN
No posts found.

When you dig deeper, you will indeed find that the public reason for these kind of restrictions is "to keep the user safe".

They claim to be worried about malware installing their own extensions, so they lock everything down. As if that same malware wouldn't just patch the firefox binary to allow loading unsigned extensions.

It's ridiculous and obviously meant as a first step towards a walled garden. It's very unfortunate that firefox followed google in this.

The answer is yes. Murdering other humans who have no way to see it coming and no way to defend themselves is deeply evil. Especially when you factor in the murder of innocents (also referred to as collateral damage), and the facts that mistakes happen.

Go 1.20 released 3 years ago

Because it's extremely useful to have adaptable data structures, without byzantine code generation?

- That climate change is real, and that humans are causing it

Not a political point. This is fact.

- That vaccines are effective, including the COVID-19 vaccine

Not a political point. This is fact.

- That COVID-19 is not a hoax; that it is a deadly illness

Not a political point. This is fact.

- That masks are effective in limiting the transfer of airborne pathogens

Not a political point. This is fact.

- That Joe Biden won the US presidential election in 2020

Not a political point. This is fact.

- That former Pres. Barack Obama was born in Hawaii

Not a political point. This is fact.

Any others?

As it turns out, we only run repacks on a repository network level, which means that repacks need to consider objects from all forks of a given repository.

Repacking entire repository networks will always lead to less optimal pack sizes compared to repacking just objects from a single fork. For GitHub, disk space is not the only thing we optimize for, but also performance across forks and client performance.

So the lesson here is you can DoS existing open source projects somehow by forking them and increasing the forked repo size >2GB?