I'm not exactly sure what you mean. Doesn't all dependency injection work the way I described?
Without being familiar with the framework, you can't trace your way from the class getting injected into to the configuration, even if you're experienced with the language.
Try driving twelve hours each way to see your family that lives in a town without bus, train, or air service. I doubt you'd still believe a sound system (with physical buttons) is unnecessary coddle.
Ha, abusing fork for asynchronous saves is clever. I hope they are aware of the following restriction:
After a fork() in a multithreaded program, the child can safely call only async-signal-safe functions (see signal-safety(7)) until such time as it calls execve(2).
I'd like Gentoo ebuilds to run in a fully isolated namespace/container with only the dependencies explicitly enabled by portage configuration. Something like a mix of nix but with the ebuild syntax.
You use cards for offline authentication (bars/festivals/etc.), and use a different process for online authentication.
Proving someone has the physical card in their possession (which is what a reader does) isn't really useful for proving identity when you can't also check the picture.
I mean, if you're making a railgun, maybe superconducting magnets would be useful tech to have 🤔