

Yeah, he literally changed his last name to “dotcom.”


Yeah, he literally changed his last name to “dotcom.”


Regardless of who owns it or what they do with it, those GPUs will get sold on the used market with plenty of life left. Older AI GPUs, networking equipment (eg 100GbE), SAS drives, etc have been easy to find on eBay and other sites for a long time, because data centers replace hardware long before it’s expected to fail.
Most people are recommending that you bury a conduit, and it’s good advice, but also be aware that direct-bury ethernet cable is available that can be used without conduit.
12gbps could be useful if you use port expanders to put dozens of drives on the same port, but without a port expander you’re right you wouldn’t saturate the 6gbps channel.
It’s not even about the size or complexity of the project - the code in question is wrapped in an unsafe{} block, so no one should be expecting it to have the guarantees you’d normally get from rust. It’s ragebait.
And if you prefer the cat | grep ordering, < file.txt grep foo is also valid.
LSI cards are generally easy to switch to IT mode. You should be able to find a guide on servethehome.com for your model.
This, but if you already have a SAS card in RAID mode you might be able to flash IT (AKA HBA) mode firmware instead of buying a new card.
Also, SAS cables fit SATA drives, but not vice versa. So no need to buy new cables.
Yeah, the form factor, HDMI-CEC support, and integration with other valve hardware are what really sell it. But it’s not going to be underpriced for the specs, like consoles tend to be.
RAM costs will likely affect both custom built machines and the steam machine equally.
Valve already announced it will be priced similarly to a PC you build yourself.


I’m just being realistic. Some companies will fire you over this, at it will be “for cause” so you won’t even be eligible for unemployment. If you can afford to lose your job, you can afford to buy your own phone for personal use. But if you want to take that risk, I won’t stop you.


Again, someone who knows nothing about the OS.
This has nothing to do with the way the OS works, and everything to do with corporate policy. This would be against the IT policy at most companies, and circumventing their ability to remotely manage the device could easily get you fired.


Do you really think it’s a good idea to install an unofficial OS on a device your employer owns without their permission?
I’m disappointed by the lack of Whose Line Is It Anyway references in this thread :(
“everything’s made up and the points don’t matter”


If it’s your feature branch, just revert his commits (or reset the remote branch to your local branch)? Not sure why a feature branch would be shared between devs…
Both decks of the bus follow the same [code] path. That’s a lot more like increasing the buffer size.


Birds aren’t real.
Even things like HDDs that don’t become “obsolete” in 18-24 months get sold with plenty of life left (unplanned downtime is more expensive than new hardware), but obsolescence makes it happen even sooner.