Of course, but the original commentor's claim was that writing a web browser is trivial, not that compiling an existing web browser with some minimal changes is trivial.
Displaying raw HTML? Sure a fair number of people can pull that off. Actually rendering HTML+CSS with all their many features and a performant JS engine is many orders of magnitude more complex though, which is why there are basically only three browser engines (two if you count Chromium as a WebKit fork)
Not sure why you're getting downvoted, as a graphics programmer AMD's proprietary drivers are unquestionably the buggiest which I have to work with on a regular basis. Seemingly innocent stuff which works perfectly fine on every other vendor (and on the same GPU using the open-source drivers) will cause the proprietary drivers to break horribly or run slower by multiple orders of magnitude.
Sure, but unless they can get the engines started back up in time it's unlikely to be a pretty landing unless there's a convenient runway within gliding distance.
My point was more that the SSD will likely have lower latency than an Ethernet link in any case, as you've got the extra delay of data having to traverse both the local and remote network stack, as well as any switches that may be in the way. Additionally, in order to deal with that bandwidth you'll need to kit out not only the local machine, but also the remote one with expensive 400GbE hardware+transceivers, plus switches, and in order to actually store something the remote machine will also have to have either a ludicrous amount of RAM (resulting in a setup which is vastly more complex and expensive than the original RAIDed SSDs while offering presumably similar performance) or RAIDed SSD storage (which would put us right back at square one, but with extra latency). Maybe there's something I'm missing here, but I fail to see how this could possibly be set up in a way which outperforms locally attached swap space.
In fairness, there has to be some survivorship bias here: if the members of a conspiracy don't double-cross each other and are competent enough not to expose themselves, it's a lot less likely they'd ever get brought into court in the first place.
Well, assuming you've already gone through the effort to write a custom kernel module to offload your swap pages to Google Drive, it doesn't seem like that much of a stretch to have it encrypt the data before transmitting it.
modern NVMe SSDs have much more bandwidth than that, on the order of > 3GiB/s.
even an antique SATA SSD from 2009 will probably have much lower access latency than sending commands to a remote device over an ethernet link and waiting for a response
I use a PowerEdge T620 as my daily driver, let me assure you the CPU fans at full speed can be heard clearly through 3 closed doors :P