CosmosDB has etags on every document

Why not actually running CI on your computer? Most CI system work via an agent, so you can join your laptop as a worker to the CI system?

https://docs.github.com/en/actions/hosting-your-own-runners/...

You could "favor" your own laptop as a target runner for the CI when it's your PR for example

https://docs.github.com/en/actions/writing-workflows/choosin...

If only because there are 100-1000x more system that have now tied themselves ne their data to said cloud

As a feedback, having all the examples in that gif on the readme centered around node almost made me look away without a second thought.

Why is standard etag support making the frontpage?

The Codescene product provides an in-depth analysis of knowledge distribution over time:

https://codescene.io/docs/guides/social/knowledge-distributi...

I recall seeing the linux kernel repo analysis as a show case, but I can't find it anymore.

Very cool, super useful from a jumpbox accessed via ssh for example.

Looks similar to azbrowse for azure: https://github.com/lawrencegripper/azbrowse

Bicep has the potential to provide a cross platform solution, but it’s unclear whether that’s the direction: https://github.com/radius-project/bicep-types-aws

I would not expect that to happen any time soon. Maybe they will see a chance to promote bicep more by such move. Yet until now they actively (and reasonably) advise in their docs Terraform use, if you consider multicloud and few other situations.

I would rather expect MS to declare support for OpenTofu. They don't even have to be involved in it directly.

The main work is ensuring azure providers compatibility (which is formally maintained by hashi). Add compatibility with Tofu to Azure Verified Modules [0] (a great project btw), and we have a clean way out of this by providing real help where it's most needed.

[0] https://azure.github.io/Azure-Verified-Modules/

On the fly speech translation but in the voice of the speaker

Or a different voice if the voice of the speaker or the way they talk is annoying

I wish that this was just a sdk built on top of a provider/standard. Amqp 1.0 is a standard protocol. You can build all this without being tied to a product or to rabbitMQ, with a storage provider and a amqp protocol layer.