> To standardise bowel habit between participants, we developed a Stool Hardness and Transit (SHAT) score to look at stool consistency over time. The SHAT score is the sum of the Bristol Stool Chart scores over a specific time period divided by that time period in days.
> Post-ingestion, stools were monitored and examined in search of the excreted item. The search was conducted on an individual basis, and search technique was decided by the participant. The primary outcome was the Found and Retrieved Time (FART) score.
1. Potential donors get upset that they can't make directed donations to specifically support Firefox or Thunderbird rather than the whole kit-and-kaboodle
2. Separate entity spun up to focus on Thunderbird only. Now you can support Thunderbird development directly.
3. New separate entity is now in the business of extensible AI clients?
EDIT: I went back and read the launch announcement [1]. I'll concede it does say "will also allow us to explore offering our users products and services that were not possible under the Mozilla Foundation" which could mean anything, really. And this development was funded by a Mozilla grant, importantly not by Thunderbird donors. I'm still struggling to not see this as a distraction from the core mission. I wish they'd spun up a new entity instead.
AIX is still ppc64be. That and s390x are the only big-endian CPUs I can think of which aren't end-of-life, which I think is going to be an increasing maintenance burden over time for IBM alone.
Did he write down everything he learned? That way the next person only needs to cover the intervening time period.
Conceivably LLMs might be good at answering questions from an unorganized mass of timestamped documents/tickets/chat logs. All the stuff that exists anyway without any extra continuous effort required to curate it - I think that's key.
I worked for a company that published a PalmOS app. Palmgear.com was a very important distribution channel, but so was our own website, I forget the exact ratios.
You could do "network shares" as in mount the filesystem from Linux and export over Samba/NFS/etc; it would probably also be possible to export the drive as an iSCSI device and mount HFS(+) filesystems directly from the Mac.
What I've learned from visiting my own parents is, you can alleviate the energy concern, if you (1) get solar panels and (2) ban your spouse from running the dishwasher at night :P
Sounds like this is about making .OBJs that fit in the conventions set by Win32 and the Microsoft linker. If you were using Microsoft's LINK.EXE I'd look at https://learn.microsoft.com/en-us/cpp/build/reference/nodefa... (and /Zi for the Microsoft compiler)
More generally, a lot of compiler generated code (including from LLVM IR -> native) will rely on compiler-specific runtime library functions, which aren't necessarily considered part of the "C runtime". https://wiki.osdev.org/Libgcc occupies this role for GCC-compiled code. See https://godbolt.org/z/fb75PPobz for an example (64-bit division on 32-bit x86 generates a call to ___divdi3)
"Six paediatric health-care professionals were recruited to swallow a Lego head."
reply