I don't think Firefox ever touches your user.js, I've never seen that happen or anyone complaining about it. And then it overrides prefs.js generated settings. The only time I encountered problems was with a big update failing to replace a couple of prefs.js entries, and it was some really obscure settings.
I dont think this is correct. I added the boolean security.ssl.disable_session_identifiers set to true in Firefox 62.0.3 and ran the SSL Labs browser test here: https://www.ssllabs.com/ssltest/viewMyClient.html. With the boolean set to true, Session Tickts under the Protocol Details section says false. Toggling the setting back to false and rerunning the set showed Session Tickets Yes. So perhaps you had a typo in the seeting name?
SBCL is mostly written in Common Lisp. It has a compiler that can compile itself. Part of that compiler are definitions of building blocks (VOPs or virtual operations) that describe snippets of assembly code. So as always, you use the tools provided by Lisp to create a DSL that allows you to write code as is practical for your use case.
Note, that fathers now have similar rights. There are some exceptions right around the birth, because that clearly affects women an men differently. I might also miss some differences.
But the current legislation allows both my partner and me to take out equal amounts of time (about 7 month) in the coming year (we can split 14 months, as long as they each takes at least 2 and they can overlap) with 66% compensation replacement from the state.
So the employer cannot rely anymore on a man not taking time off.
(The total amount without is about three years instead of 14 months, but only those 14 months are covered financially).
The difference is that a woman has to take time off (for health reasons), whereas the man can take time off. Economically, there is a penalty for taking time off (lower salary, lower skills, lower future earnings), its economically rational to not take time off. But only a man can make that choice.
There is the library 'libc' which is a collection of interfaces to (g)libc functions together with the necessary constants and structs [1].
There is the library 'nix-rust' [2], which aims to provide a wrapper of 'libc' in idomatic Rust.
Unlike 'libc', 'nix-rust' does not have a consistent code quality and organization yet. However, Both are missing various bindings for various platforms.
