TortoiseWrath

Oh shit does lemmy not have response caching? Yeah, that’s gonna be an issue pretty soon.

hh3tf.golden.exe is 1536 bytes, compiled from C, and comes with a comma and exclamation point:

I’m actually surprised it’s that large, but Windows gonna Windows.

I wonder if YouTube still uses Python to this day

We do not.

Yeah, but I think the current iteration of Chat is the first one to be offered as an enterprise product, and the first one universally used internally (even some SRE teams are now using Chat by default instead of IRC). I could be wrong - there are some that are before my time.

That said, specific features within Chat seem to come and go quite frequently. In particular, don’t rely on any particular threading model…

“Oh no, now my phone will be 5% thicker!” - what the phone companies pretend to think I think about this

Not relevant to lemmy (yet), but this does break down a bit at very large scales. (Source: am infra eng at YouTube.)

System architecture (particularly storage) is certainly by far the largest contributor to web performance, but the language of choice and its execution environment can matter. It’s not so important when it’s the difference between using 51% and 50% of some server’s CPU or serving requests in 101 vs 100 ms, but when it’s the difference between running 5100 and 5000 servers or blocking threads for 101 vs 100 CPU-hours per second, you’ll feel it.

Languages also build up cultures and ecosystems surrounding them that can lend themselves to certain architectural decisions that might not be beneficial. I think one of the major reasons they migrated the YouTube backend to C++ isn’t really anything to do with the core languages themselves, but the fact that existing C++ libraries tend to be way more optimized than their Python equivalents, so we wouldn’t have to invest as much in developing more efficient libraries.

I moved my .dev to NameSilo to live with the rest of my domains, since luckily that’s allowed now. See here for the list of options if you have any Google Registry domains (.dev, .app, .new, etc.). Make sure to uncheck “Show preferred partners only” if you don’t care which ones have given Google more money or whatever that means.

FWIW the comms I’ve seen suggest Squarespace has agreed to actually offer standalone domains as part of this deal… I doubt that’s binding in the long term though, and they’ll certainly want to get people to use their signature site builder product.

I know Google Cloud Domains (previously separate from Google Domains) is being deprecated too, but I don’t know if those domains are also automatically moving to Squarespace. Seems weird if they do that, since it would drive people directly to one of Cloud’s main competitors… but they’re driving people away from Cloud anyway with this so ¯_(ツ)_/¯

I imagine the ones the middle managers use internally are safe… that is, the main Workspace apps (I think that’s what they’re called now? you know… Docs, Sheets, Forms, Slides, Calendar, Chat).

And the few Cloud services that are actually running things like YouTube (Spanner, … actually I think that’s the only publicly available one)