We sacrifice our time with our children for future career earnings to maximize lifetime income. People in this discussion throw around terms like GDP growth due to increased labour market participation from working moms...
It's ok just to accept what's happening. its not like you don't know what you're doing. Life is full of unpleasant tradeoffs.
I think you're overestimating how good parents some people are.
In Quebec they moved kindergarten down to 4 years old because they realised some kids are very "under-stimulated" at home and it sets them for failure for their whole academic career.
Die hard rust fans often minimize the very real developer difficulty incurred by their language of choice. Even major library maintainers in rust have criticisms of various language features because of their difficulty to use. These are real and substantiative concerns that would affect any development team not made of expert rustaceans. Just look at basic dynamic programming implementations in a normal language versus rust for say popular leap code questions and you'll see the difference in basic developer productivity.
People who are really interested in rust tend to be top-tier developers. I don't think they're consciously lying about their experiences working with the language but they may not hit the speed bumps that normal people would. My personal abilities make me competent in golang, ruby, python, java, c++. I love the quasi-functional styling of rust but whenever I've tried to build small projects in it I've gotten bogged down in fighting with the compiler in ways I never do in the former. It is fast as all get out tho!
Saving heirloom apples has zero biodiversity value, or near two it. All domestic apples are extremely inbred and from a one or two cultivars brought to Europe a few hundred years back. The reservoir of apple biodiversity , at least for sylvestris is in its native range where domestic apple cultivation is actively polluting the genome. I think that's like khazakhastan and western china.
In go, you either handle the error where it happens or close to it, or log it. No need to pass things up just to log. I like the simplicity, and the zero cost at runtime. If you could handle the error in another lang you could handle it in go, or youd just supress or log it anyway.
In a microservice, almost all errors are handled by doing nothing and returning the error to the caller. Retrying may be an option, but you have to be careful not to make your system into a cascading failure amplifier.
