In most practical applications that I've seen fractions of imperial measurements used, it tends to be in powers of 2, i.e., 3/16 inch, 1/4 mile, etc. Decimals can certainly be used, but for most applications where you'd use something like a "millionth of an inch," it's vastly more common to use metric.
What applications are you talking about? Just for a general example of the sort of thing I'm talking about: https://youtu.be/EWqThb9Z1jk?t=137
They're resurfacing a surface plate, which has to be very flat. If you listen to the exchanges between them, everything is being done in millionths of an inch.
In my experience (electronics manufacturing), both PCBs and machined parts are usually in mils or decimal inches, although millimeters are becoming more common and many drawings show both systems.
Written Japanese does to be a quite a bit more dense than written English, especially if it's heavy in kanji (Chinese symbols), where a single character represents a word or concept and can be several syllables in length when spoken. It's enough of a factor that, back in the 16 bit era when you only had a few MB of storage space to work with, there were several old JRPGs that either needed to have a lot of dialogue cut out in translation to still fit on the cartridge (e.g., Final Fantasy 6), or that were simply never translated at all because it would have been futile to try (e.g., Final Fantasy 5 and Seiken Densetsu 3, according to legend).
However, this page isn't really the best example of that because nearly half the text is actually English loanwords written in katakana (the Japanese syllabary), which is only slightly more dense per character than English, since each character usually represents a consonant and vowel together. So in this case I'd say the Japanese page carries a little more information, but not drastically so. The copy itself is also quite different, though.
Personally, I think in a perfect world there would be a more widespread distinction between "save" (something that happens automatically whenever changes are made, to "save" the data from some unexpected calamity like power failure) and "commit" (what you're talking about, which most people think of as "saving"). I doubt it would realistically catch on any time soon outside of tech circles, though, due to the confusion it could cause the average user - "New, open, print, commit, exit... now where the hell is the damn save button?!"
Actually, it's the concept of 'save' that is unintuitive. The EPOC systems just kept your data, and it's one of the nice features that sublime gives you. In an ideal world, a document would keep its entire change history as a graph (not just a single line), and you wouldn't 'save' a copy, you'd name a particular revision of it so that it was easy to get back to later.
Show them how much money they can make if they stick with it. Spending a solid year and maybe a hundred bucks on books to teach yourself how to code can easily get you a higher starting wage than a lot of people with bachelor's degrees and tens of thousands in student loan debt.
They need to be intrinsically motivated or else they will be B or C players. I'm only interested in cultivating A players. It's something I can't do, and it's something that would be extremely valuable to any organization (like any company I run for instance.)
