"I'm sorry" can mean "I am apologizing" but often it instead means "I feel bad". It depends on context which applies.
"I'm sorry for how you feel" without more explanation often sounds like "The thing that makes me feel bad in this situation is your reaction to it". It can come across as blaming the person for the feelings, regretting not being able to control others' feelings better, or dismissing the root causes of the feelings and any agency in them.
It's a bad apology because of the ambiguity, though passive aggressive types like that aspect. It's honestly a bad way to sympathize as well.
Counterpoint: Shaded spots at work parking lots in Texas fill up the fastest. Conspicuously so. Also, use of windshield visors is much more prolific than in cooler climates.
I can't believe your Texan friend never noticed those phenomenon.
> In what way(s) does Rust's C interop depend on cargo?
Do rust and cargo allow for multiple interpretations of the same C header file across different objects in the same program? That's how C libraries are often implemented in practice due to preprocessor tricks, though I wish it wasn't normal to do this sort of thing.
For simple scripting tasks, yes. I have had the opposite experience for more critical software engineering tasks (as in, coding integrated over time and people).
Language aside, the ecosystem and culture do not afford enough in way of testing, dependency management, feature flags, static analysis, legibility, and so on. The reason people say to keep shell programs short is because of these problems, it needs to be possible to rewrite shell programs on a whim. At least then, you can A/B test and deploy at that scope.
There's a flip side to consider, though. I've seen brilliant people waste years of their energy and talent on technology ideas that go nowhere due to a lack of ability to ship to a community and gain mindshare among relevant technologists. Folks should dismiss vanity and puffery, but broadcasting opportunities and successes (and interesting challenges that need solutions, even) is undervalued among certain engineers. And it's a critical part of "shipping" for certain kinds of projects.
> It was always clear that there was a huge misconception about what unions are, and how they work, based on the depiction of unions in popular culture or the past.
Police and teacher unions are very much current events in the U.S. between COVID and the protests.
...you're just overanalyzing what I said. I just meant that git stays out of the workflow business and higher level tools might be able to fill in the gap.
I'm not sure I'd use this tool, but I'm not going to get upset if people like it.
I agree, but it's also true that many companies have official (as in HR required training) opinions on certain topics. In that case, there's already a "discussion", but a one-sided one. Maybe it's the right side, but it's not like we really enforce a hard line between philosophy/ethics/politics and work.