Can't you avoid the OSD if you control it with DCC?

Seems they come with 200gbit ports so it takes 20 minutes to fill memory.

500 nits is not really good enough for laptop that you might use outside.

Luckily they are still improving and we now have Tandem OLED with about double that.

Should a laptop be optimized for indoor or outdoor use?

Given the primary selling point of laptops is their portability (often at the cost of other things), they should be optimized to be highly usable wherever they might end up getting used.

And if not mise, just a Makefile, shell scripts or custom docker images. Then you can run and develop them locally.

GitHub actions has some rough edges around caching, but all the packaging is totally unimportant and best avoided.

They are usually shaped to fit in exactly the space available to maximize capacity. Standard cell sizes wastes space.

Besides it's pretty easy to get custom battery pouches made.

Who will make these custom battery pouches for old phones though? Think my old Poco x3 pro, not the iPhone 17. I am sure there are tons of people willing to make batteries for the iPhone 17 but I feel like the interest wanes as the phone gets older?

For older phones, the batteries we buy are likely also old stock left over if we can find some in stock anyway, right?

Servers can support it but not browsers.

That doesn't match what I see. Shops don't issue an invoice until the product ships, well after payment.

Victoria metrics which has similar database design to clickhouse is good for metrics.

But it doesn't have a complete dashboard UI like Grafana.

Just to add, VictoriaMetrics covers all 3 signals:

- VictoriaMetrics for metrics. With Prometheus API support, so it integrates with Grafana using Prometheus datasource. It has its own Grafana datasource with extra functionality too.

- VictoriaLogs for logs. Integrates natively with Grafana using VictoriaLogs datasource.

- VictoriaTraces for traces. With Jaeger API support, so it intergrates with Grafana using Jaeger datasource.

All 3 solutions support alerting, managed by same team, are Apache2 licensed, are focused on resource efficiency and simiplicity.

I find it quite hard to follow PRs when there is a lot of rebasing. I don't really find separate non-time-based commits useful.

So I agree but unfortunately it's the norm and policy for some clients.

Git-absord by default doesn't squash the fixups though, it creates new ones with special tags for easy rebasing later.

That hasn't been true for at least 15 years. I was a k-root DNS operator then, and we ran several software stacks on each cluster in case one had a bug.