They should have mandated markings on the plugs that indicate what the cable supports.
Let me know when someone gets an LLM to run on a Bendix G15. This Pentium stuff is way too new.
The consumer grade 2.5" drives may be half empty, but the enterprise grade ones are mostly heatsink so they don't thermal throttle within a minute of heavy use. M.2 drives are way too small. It was fine for SATA speeds, but not for the PCIe 5 NVMe drives.
I would rather have the network switch.
There's only so much power you can put through such a small connector. I could certainly see a high end gaming laptop requiring more than 240W since GPUs keep getting more power hungry. They could increase the voltage a bit, but I doubt they will go much higher.
SATA SSDs are still more than fast enough to saturate a 2.5G ethernet connection. Some HDDs can even saturate 2.5G on large sequential reads and writes. The higher speed from M.2 NVMe drives isn't very useful when they overheat and thermal throttle quickly. You need U.2 or EDSFF drives for sustained high speed transfers.
There's not much room for any open programs on that panel. Why didn't you use a dock for the launchers instead?
I would hope that a device capable of pulling 200w from USB would be intelligent enough to detect the excessive voltage drop and error out or reduce the current.
My server with 8 hard drives uses about 60 watts and goes up to around 80 under heavy load. The firewall, switch, access points and modem use another 50-60 watts.
I really need upgrade my server and firewall to something about 10 years newer, it would reduce my power consumption quite a bit and I would have a lot more runtime on UPS.
Yeah, that's not a prank. That could have killed people if nobody noticed it.
I hope they lock his dumb ass up for a long time.
You can do almost anything with a website that you could do with an app. The only reason they are pushing the apps so hard is because they can collect a lot more data than a website can.
You don't need 64 bit programs or CPUs to fix the 2038 problem. You just need to use a 64 bit time_t. It will work fine on 32 bit CPUs or even 8 bit microcontrollers.