That’s an awful thing to have gone through, but they are sometimes in a lose-lose-lose situation wrt insurance(s)-best practices-community concerns.
Maybe the patient’s insurance requires certain conditions to be met. Depending on the drug even expressing you’d be ok paying out of pocket can be dicey.
Maybe their malpractice insurance has some conditions based on actions of this doctor or not even this doctor but their insurance pool.
Maybe the hospital, state, school they are at or went to has procedures that just weren’t met for whatever reason. If you are dead set on getting or trying a particular treatment I have found it useful to know what these are. This can backfire spectacularly though if they suspect they’re being played. (Which is an additional related meta game).
And then there are societal/community issues. We aren’t in the time of just using antibiotics whenever something comes up as suspect. We are running out of effective antibiotics for some strains. Having had a resistant bacterial infection I wish people had had more restraint.
Learning to play the medical game or even realizing there is one is extremely upsetting. Doubly so when dealing with sudden life altering conditions. I got mad at it too. But that also didn’t help me, until I realized it’s just a big system like any other.
I don’t think it’s microkernels in general but their microkernel design which wants as much as possible in userspace. They want each component to have its own memory space. ZFS blurs the layers between filesystem and the volume management. This kinda bothers layers of abstraction model folks. And I assume combined with their posix like model it just sorta clashes with what they want to do. Not impossible to integrate, but they want something a little different.
Very interesting project, I wish I had gone down this route instead of the undocumented hell of usb PTP with hundreds of edge/corner case work arounds.
The fact that USB ptp is some baseline is kind of exceedingly great, even if yeah in practice it'a a huge mess of vendor extensions tacked on. I like trying to have some collaboration & specs! It's a monster oh sure but gphoto2 probably wouldn't have come about, as a sick compendium of all camera backs & vendor extensions, if there wasn't a common thread, common binding for cameras! Once you go from USB to IP you're (generally) untethered unmoored from anything shared!
What's done here is super admirable & super neat. But it's even more spelunking into the unknown than USB ptp imo! Thankfully there's some pretty old school direct on-the-line protocols that are kinda just working!
It's interesting to me at least to navel gaze over. The attempt to have common tools versus the just doing whatever.
One of my favorite connectivity solutions ever was the Nvidia Shield Controller (2015). A wifi (wifi direct/wifi-p2p at that!) video gaming controller. With audio that uses ozproto's stack, a usb-over-ip setup! Something about just tunneling USB being conceptually easier to reason about & do than deciding what IP services to make for a controller is so elegant and neat and weird. https://github.com/devmapal/nvidia-shield-controller-driver
When reverse-engineering some of the Samsung NX camera firmware files, I found USB-PTP code that implements different custom remote commands <https://chaos.social/@ge0rg/114723076401717110> but I'm not deep enough into PTP to make sense of them.
Is there anywhere a group focusing on understanding and re-implementing custom PTP protocols?
It is surprising that after all these years, there is still no good way to transfer files between two devices over USB. MTP exists but it was never widely supported and it seems like even the support it did have is slowly rotting as the answer became just connect everything to cloud storage.
reMarkable tablets end up exposing a USB ethernet device with a /23 private subnet and listing an IP address to visit in a browser. It works much more reliably than it should.
It’s specialized knowledge, hard to do “correctly” (read posix here) but obtainable and implementable by a small team if you pick your battles right. Also supporting very specific use cases helps a lot.
It’s also pretty easy to justify as the hardware and software from vanguard tech companies is outrageously expensive. I used to develop software for a blue colored distributed filesystem.
There’s also weirdness with the drivers and hdmi, I think around encryption mainly. But if you only have DP and include an adapter, it’s suddenly “not my problem” from the perspective of Intel.
Additionally, topical is not FDA approved. While not necessary for research it adds typically unwanted complications to studies.