880 karma · joined July 8, 2007
This is an stm32l432kc in the form of a yubikey nano.
https://www.aboutamazon.com/news/aws/aws-liquid-cooling-data...
In either case I cannot find out how they dump the heat from the output water before recycling it. That's a problem I find far more interesting.
https://blog.google/outreach-initiatives/sustainability/gett...
My main motivation was to implement a service that publishes the addresses of containers and vms that I run on my workstation to my local network, but it gradually has grown into a full-blown implementation of RFC 6762, which has been fun.
There's also probably some savings around not having to convert between the structures used by gethostbyname and DNS questions&answers.
It was so jarring I couldn't watch it and switched to Japanese with subtitles. Their mouths looked so stiff and unnatural and out of sync with their expressions that all me and my wife could talk about was how bad it looked.
Much of today's software is going to be nothing more than a memory 22 years from now, after their authors run out of funding and they turn down the saas infrastructure that they shoehorned into it for that sweet, sweet recurring income. And more likely than not, we'll still be able to run this program from 2002, in 2046.
I use guix myself and prefer its use of scheme. I don't mind having a little less guidance and "how-to" articles available if I'm trying something new because I'm comfortable reading its codebase.
Moreover, if you are in the cloud, part of your infrastructure is not under your control, making it even harder to reproduce a problem.
I've worked with companies at Netflix's scale and they still have last-resort ssh access to their systems.
Current implementations have some disadvantages to TCP, but they are not inherent to the protocol, they just highlight the decades of work done to make TCP scale with network hardware.
Your points seem better directed at HTTP/3 than QUIC.
The coding style is a little terse and is clearly influenced by djb. The author has some (justified) mistrust of the C standard library, so you'll need to get used to the alternatives in their "skalibs" library, but I'd feel much more comfortable debugging a problem with this suite than I would with systemd.
Also, the related tool, execline, is a trip: https://skarnet.org/software/execline/ .
I suppose it could make a difference on lossy networks, but I'm not sure.
A bigger reason you want multiple streams is because most network providers use a stream identifier like the 5-tuple hash to spread traffic, and support single-stream bandwidth much lower than whatever aggregate they may advertise.