watermelon0

In my experience, migrating between Apple Passwords and Bitwarden worked without issues, in both directions.

> we take the total likelihood of those moments of greatness to (->from) “definitely sometimes” to “never”.

> Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods (http://en.wikipedia.org/wiki/Cuisenaire_rods). I grew up and today I use monochromatic numerals.

https://groups.google.com/g/golang-nuts/c/hJHCAaiL0so/m/kG3B...

He is definitely not alone in thinking this, for example (but for different reasons): https://www.linusakesson.net/programming/syntaxhighlighting/

There are hardware cheats that are not detectable by KLAC, so it doesn't solve the problem, just improves the situation.

The only way to avoid cheaters is to play with people you trust.

Actions management plane is the most problematic part of the platform (in regards to scale), so they are basically losing money with self-hosted runners.

Scaling of VMs shouldn't be a problem, since that is practically stateless, whereas there are lots of operations performed for every job/workflow.

I'm not blaming the Homebrew project/developers here, but the fact that many people are okay with deprecating perfectly fine hardware.

Seems like reader mode is needed due to bad defaults.

However, Codeberg offers hosted Woodpecker CI.

(Cloudflare says I'm blocked from accessing the webpage, even though I'm using a residential IP)

Also, it's not like 860-930 MHz (depending on the country) is without interference.

Additionally, Docker/Podman/Orbstack start a single VM, where memory is shared between containers.

On the other hand, Apple Containers create a separate VM for each container, which results in higher memory usage due to Linux kernel overhead, as well as the fact that kernel will try to use most of the available memory for file caching.

I've been using Hetzner for many years, both personally and for business use, and I've not seen any noticeable issues regarding the latency.

Granted, my use cases are webapps/backends that are not particularly latency sensitive, and are primarily used from a few European countries.

For what's worth, I've seen cases where download speeds from Hetzner are considerably higher than from AWS eu-central-1.

Generally, you don't want to award people/companies that don't respect you. I'm not saying that you shouldn't re-evaluate them in the future, but they will walk away with the wrong lesson if you just start throwing money at them.

Invoices are legally binding documents in many countries, and even if that might not be the case in your country, not everyone might be aware of that fact.

> since it gives their AP team a real cost to work from instead of a ballpark of us vs. GitHub

Same could be achieved by showing the real cost in the web app and/or sending a report via email, without scaring them away, and possibly _extorting_ them.