Where I work in software development, we were about to undertake writing a pretty large application from scratch. Mostly, the company was a Java plus Spring shop with a few exceptions. One team wrote almost exclusively Python, for instance. But as far as I knew, there wasn't any specific policy requiring the use of any particular language.
So as a team, we pushed to write our new project in Python. After all, there was precedent for Python projects and Python was definitely appropriate for our use case.
The managers took it up the chain. The chain hemmed and hawed for months, but eventually made a more official policy that we had to use Java (and Spring).
That's interesting. I'd be a little concerned that widespread use of that might create more legal issues for Archive.org that wouldn't be problems if it never caught on much. On that basis, I'd probably not use it.
But I'd imagine ideological opposition to such a thing wouldn't be enough to keep it from catching on either.
It depends on your specific case, of course. That 0.4mm is indeed a good rule of thumb. But also, assuming you're dealing with FFF-printed parts, generally if the two parts slide together along the layer lines, it'll feel just a little looser than if they slide together perpendicular to layer lines. That's just due to the ribbed texture inherent to FFF printing. Though printing at smaller layer heights will reduce that effect and also make the parts fit just a little looser over all.
Aside from that, probably the best advice I can give is:
Look, I right-clicked $1.2 million.
"I"
"could"
"stop"
"any"
"time"
"I"
"want."
Did you really say that with a straight face? I thought that was just what people said to mock people who were clearly addicted.