fiberstore has them as well, plus you can buy modules, DACS and everything programmed to the vendor of choice, including different vendors on each end
Especially handy for specific Intel NICs where they refuse to link up if the module isn't in the driver-allowed list and those modules are hard to come by
The DDX3216 was such a nice piece of tech to work with, sure it had its flaws, but compared to what else was out there the value was just insane for the time.
Most devices still support S3 sleep, it's just disabled by default as s2idle (modern standby) has become the default. You can almost always re-enable S3 sleep if you really want to, but on modern devices it typically only takes a few seconds to resume from S4 (suspend-to-disk) which technically is safer and more reliable. Also you can always use suspend-then-hibernate if you really want fast resume during the day, but long battery life when it's more than an hour or so.
So fun seeing all these familiar names pop up in a single thread, haven't been active in video after leaving Kaltura but have fond memories of FOMS/FOSDEM and meeting all of you!
Give it an image, get back a URL, scale to zero when there’s no traffic. The platform handles isolation, routing, and resource limits. The user handles their app.
Only if there's a commercial incentive to do so methinks. Just one of the things where I expect a legal catch-up is needed to get companies to do the right thing.
If you work at AWS in a technical role you can check the capacity of each pool in each AZ using an internal tool. Previously the main reason for pool exhaustion was automated jobs at the start of each working day as well as instance slotting issues (releasing a 4xl but only re-allocating a l means you now cannot slot another 4xl).
All the big ones have talked about their storage systems, but have been reluctant publishing papers like they used to do, so it appears to be more of a marketing focused effort than trying to share the technical details with the world.
Maybe the problem for Intel is complacency exactly because there is this expectation of a bailout when things don't go to plan.
While other hardware companies got lean operationally and employee wise Intel did not. The ex-Intel employees all paint somewhat the same picture of bureaucracy, layers of (poorly managed) dependencies and reliance on paradigms that worked during late 90s / early 2000s.
If you followed sources like semiaccurate the situation at Intel is not surprising either, they've been reporting on issues there since their inception.
The YT Premium subscription suffers from being low value imo, forced bundling with YT Music which inflates prices, and little to no synergy with Google One subscriptions in most countries.
Especially handy for specific Intel NICs where they refuse to link up if the module isn't in the driver-allowed list and those modules are hard to come by