Not to shill for a company, but probably because it's rated to work with it. Similar experience you get with "enterprise equipment". "You could use any other drive, but our drive has been through rigorous testing" kind…
Already using it on a 3 drive gaming PC on NixOS and it's been great so far. The caching algo massively speeds up interactions and load times. Hope you continue the good work and best of luck.
Given that banana countries were a thing, I think it wouldn't be completely out of character for the US to enforce it's (it's own companies) interests. But I don't think it will be war, but rather soft-power.
To be fair to them, some Linux defaults are atrocious IMHO. For example mq-deadline ALWAYS performs badly in desktop tasks. Launching a Steam download alone is enough to kill a Linux machine using that scheduler.…
Unfortunately it tends to do so randomly (was using foot for like 3 or so years by now). And in the end you'll only ever end up saving single digits of RAM. I suggest using server mode *only* on a RAM constrained device…
Same here in Serbia, I'm guessing this document is being geo restricted via IP.
I've already made this into a all-in-one program: https://github.com/nikp123/wake-on-arp/ but i do agree with the others in this thread, it's quite a hassle to keep this setup working as intended. I'd advise against…
Not to shill for a company, but probably because it's rated to work with it. Similar experience you get with "enterprise equipment". "You could use any other drive, but our drive has been through rigorous testing" kind…
Already using it on a 3 drive gaming PC on NixOS and it's been great so far. The caching algo massively speeds up interactions and load times. Hope you continue the good work and best of luck.
Given that banana countries were a thing, I think it wouldn't be completely out of character for the US to enforce it's (it's own companies) interests. But I don't think it will be war, but rather soft-power.
To be fair to them, some Linux defaults are atrocious IMHO. For example mq-deadline ALWAYS performs badly in desktop tasks. Launching a Steam download alone is enough to kill a Linux machine using that scheduler.…
Unfortunately it tends to do so randomly (was using foot for like 3 or so years by now). And in the end you'll only ever end up saving single digits of RAM. I suggest using server mode *only* on a RAM constrained device…
Same here in Serbia, I'm guessing this document is being geo restricted via IP.
I've already made this into a all-in-one program: https://github.com/nikp123/wake-on-arp/ but i do agree with the others in this thread, it's quite a hassle to keep this setup working as intended. I'd advise against…