I use these guidelines all the time in the PDF format for free, and I'd love to have these in a structured format. For $3000/year you could get 50 users access to PDF prescription templates to speed up their work. That's not bad, but it's still all PDF.
For the nice low price of "contact us for pricing," though, you could have EMR integration. They couldn't justify $$$$ for EMR integration if all this information is easily accessible.
Came here to say the same. The shipit program relieved a major pain point that prevented me from getting into Linux at the time: dial-up networking. It was a clever idea :)
This is more similar to iVentoy, which implements PXE boot, but is closed source. netboot.xyz, on the other hand, requires boot images to be extracted and served in an iPXE-friendly format, which their CI/CD system does automatically. These solutions are good for facilitating OS installations across a fleet of computers on a network.
But for system rescue purposes, Ventoy still wins. You bring your own boot images, which could be arbitrary ISOs, and don't have to worry about networking availability.
It's not surprising that seeds need little more than moisture, earth-like atmosphere, and gentle heat to sprout. They contain all the nutrients and instructions required to start new life.
It's also not surprising that too much frass would inhibit growth. Even in earth-like soil, too much fertilizer is toxic.
But it's good to know that Mars-like soil doesn't inhibit plant growth.
I agree with you about YAML's treatment of tabs. I still use YAML because there's often no other choice.
Python is actually flexible in its acceptance of both spaces and tabs for indentation.
Maybe you were thinking of Nim or Zig? Nim apparently supports an unsightly "magic" line for this (`#? replace(sub = "\t", by = " ")`), and Zig now appears to tolerate tabs as long as you don't use `zig fmt`. I haven't used either yet because of the prejudice against tabs, but Zig is starting to look more palatable.
> I agree with you about YAML's treatment of tabs. I still use YAML because there's often no other choice.
True, I'm using it too when I have no other choice.
> Python is actually flexible in its acceptance of both spaces and tabs for indentation.
True but it does give constant warnings then which is annoying. And I was worried about it dropping support in the future so I didn't want to waste time learning it.
Even the camshaft-crankshaft system could be considered an analog computer that renders (in realtime) the positions of the valves based on the phase of the pistons. Any car with an internal combustion engine has "computers."
Hobbyist effort is human labor for the hobbyist's benefit, not someone else's benefit.
If the Kolibri OS folks experience unique enjoyment from developing this project that they would not obtain from Menuet OS, then the labor would not be duplicated.
I use these guidelines all the time in the PDF format for free, and I'd love to have these in a structured format. For $3000/year you could get 50 users access to PDF prescription templates to speed up their work. That's not bad, but it's still all PDF.
For the nice low price of "contact us for pricing," though, you could have EMR integration. They couldn't justify $$$$ for EMR integration if all this information is easily accessible.
https://www.nccn.org/compendia-templates/nccn-templates-main...