You have to be kidding me
He in explained in precise detail how the SSD was designed, how it differs from standard SSD's, how it's superior than current SSD's, how bottlenecks were removed, how latency were removed, why they chose 12 channels 6 priority levels instead of the normal 8 channel 2 priority levels of every other SSD. How they customized the I/O with features no other SSD has. He did this all without using BS misleading fancy prettied up words based on software.
Where's the MS equivalent of this? Where is the in depth breakdown of their SSD? All i'm seeing are words for software made stuff to fool people into thinking their fairly standard SSD is on par or better that PS5's clearly better SSD.
Pretty embarrassing that a, as you claim, mediocre game developer outclassed an entire company that, as you also claim, made the computer what it is today.
You can't remove latency altogether, even SRAM has latency. You can only reduce it, and I'm sure Sony have done this. But there is some evidence pointing to MS having done this moreso. And you don't necessarily need extremely low latency for bandwidth-happy solutions and we know Sony have a particular focus on maximizing bandwidth saturation, MS less so.
MS haven't done a singular video presentation wrapping all their XvA stuff into a nice 40-so minute video file, but they have mentioned a lot of things about it already. Some of it you have to search around though, such as various Twitter comments (and other things in certain interviews, like with the GPU mesh shader level support, which is 256. Conversely, Nvidia mesh shader level support is 128).
Most of what they have mentioned actually has technical research and implementations that support it, so it's not necessarily words of PR fluff (it is being presented in a way to enable good PR though, obviously. But Sony does this as well, Cerny even did a bit of it in Road to PS5 presentation). If you pay close attention, Cerny did clearly spin some mentions when it came to even certain parts of the SSD I/O, such as terminology like cache coherency
engines. Using
engines in that context is an emotive appeal, to convey power. It's certainly powerful for what it is, but an exaggerative term like engine needn't be used. There was more of this in their GPU portion though particularly with downplaying certain aspects of GPU design they knew a certain competitor had an advantage in (while hoping those who were listening would ignore patterns in vast majority of GPU benchmarks).
If you're waiting for a full system architecture dissertation on Series systems, you'll most likely have to wait until August 17th, when the Hot Chips presentation is held.