795 karma · joined May 5, 2014
F21A6194C9DB9899CD09E24E434B2C14B8C33422
[ my public key: https://keybase.io/n8henrie; my proof: https://keybase.io/n8henrie/sigs/WoQvsZKguJVoMfO7Fxk2mnWhN1Xh0cLZuDGQnxpwhWY ]
I wonder if other factors like glucose level could affect both osmolality and cognition?
Would be much more interesting as a randomized trial (though I'm not sure what would make a good placebo intervention as a control).
EDIT: And I wonder if nix can (easily) be configured to use `rust-lld`... anyone know off-hand?
So in short, I thought they basically just helped your devices find each other (and connect to each other directly), not currying any of your traffic. Which is how they can give people so many free devices (100 currently) -- because it doesn't really cost them any work / network load.
Also your devices connect directly over your LAN if possible, which goes against traffic flowing through them.
Please let me know if my mental model is wrong here, I'm certainly no network engineer.
And what command line tool are you referencing?
Unfortunately it seems mostly to be a money grab in many specialties, with passing rates in the high 90s for recertification exams, fees of over a thousand dollars, and often with multiple retries if one fails (as long as you pay the fee for each attempt).
It is one huge reason I work as a federal employee -- FTCA helps me feel free to do what I think is right for my patient without worrying nearly as much about getting sued. In my line of work, a tremendous amount of absurd testing is done because there could be a 0.01% chance of missing something serious, and if you see 1,000 pts per year and plan to have a multi-decade career, it's easy to justify almost certainly unnecessary testing.
Sounds like the author did not specify the correct version of a dependency. It should not be surprising to find an incompatible API if using a (presumably) different major version number of a dependency, right?
I would say that failing to compile seems like a best-case scenario here. Serious question -- what would have been a better result in this situation?
I have found disappointing performance gains rewriting my small Python projects in Rust as most time is spent in IO and many / most CPU-intensive tasks in Python are done in C or C extensions that release the GIL and seem just as fast as Rust would be.
No doubt the improved responsiveness / startup time for rust CLI apps is much appreciated, and it is trivial to intentionally write a very poorly performing CPU-intensive task in Python.
In contrast, it's pretty difficult to prove that an ear infection was not present at the time of evaluation. The assessment is highly subjective, can be really difficult to thoroughly assess in young kids, and generally doesn't leave any hard evidence to review or critique.
Nearly all of the bad incentives align to pressure providers to just diagnose an ear infection and prescribe the antibiotic and move on with their busy shift.
> Going for a run might is good for your heart
Doesn't seem like this went through much review?
Trying to keep him on open source games that run on his Manjaro MacBook Air (11", 2014?).
Other hits include Minecraft, SuperTux, and SuperTuxCart, 0ad, and he just loving OpenRA and OpenRA Combined Arms!
So my 128GB server seems unlikely to benefit much.
Not to try to correct the author here, but it supports geckobrowser as well (not just chromium-based), right?
I'm currently trying to package for nixpkgs[0] and am using Firefox for the checkPhase.
And to be fair, 2 of 3 were only suspicious for having a hardware problem so I replaced with a larger drive (and was super nice to have such a straightforward was to expand the size as compared to ZFS).
My NAS and several larger datasets are on ZFS based on reputation alone, but honestly I've had more data loss scares with ZFS than BTRFS (drives that have disappeared for no reason then reappeared hours later, soft locked and unable to unmount indefinitely, several unfortunate user-error issues with automounting datasets overlaying necessary top-level directories and preventing successful boots), and I find the BTRFS tooling more intuitive.
For my hobbyist-level homelab type needs, I would say I'm overall pretty happy with BTRFS. The only issue I've never been able to resolve is regarding lockups when issuing quotas -- another reason I stick to ZFS for my spinning rust storage drives.
Oh, and the ZFS ability to mount a zvol as a foreign filesystem (words?) lets me `btrfs send` backups to ZFS, which is nice!