big L for all the cloud providers that made the mistake of using it instead of forging their own path, they're kind of screwed now

How are they screwed if they can adopt the source and continue patching it? Writing their own would incur a greater cost.

option 2 is what this blog is about, the example code creates a socket using that method

HR, finance, sales any non engineer is called an operator these days basically

i think its a bit of a VC lingo that i dislike seeing adopted by actual... operators. it casts the world into two: either you own a business, or you operate one. that makes it look like a 50-50 choice that is usually a valid option for a privileged few. also if the world actually looked like that then we'd have a lot less building going on and there are too many VCs already.

instead I propose to call VC's "non-operator characters" and see how they feel about that

Could you how a decimal point in the distance measuring tool? I want to measure distances in my backyard from the satellite photo and the rounded number makes it hard to be accurate

Good idea, I will add it! I did that before for Area tool but it's missing in distance tool. Thank you for the feedback!

Ah this makes a lot of sense, perhaps the posted flag doesn't get reset e.g. if this branch gets followed: https://source.chromium.org/chromium/chromium/src/+/main:v8/...

Prefab stone strips are used here and there but most brick facades are still built by hand on-site.

There's a huge shortage of workers, which is why we're working on this.

Thank you!!

Has anyone be able to find any other dock/display with video, 2.5gbps and PD?

I've been using this for a few months:

https://www.amazon.com/SIIG-Universal-USB-C-Docking-Station/...

Works great! I connect to it with 1 USB-C cable, and it charges the laptop and drives up to four 4k monitors, and it also has 2.5gbps ethernet. Love the convenience of it all.

Yes, I count at least 35 on: https://dancharblog.wordpress.com/2024/01/01/usb4-tb4-docks/

Hope this is upstreamed at some point. Good to see there's still a lot of gains to be made for Rust compile time

Wouldn't this be quite difficult to upstream to users in the state presented?

At the least you'd want to make caching opt-in per macro unless something special was enabled. Forcing the end developer to blacklist incompatible macros feels like an anti-pattern.

Really wish this existed in the Netherlands when I was growing up!