"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.

I can't believe your Texan friend never noticed those phenomenon.

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.

I'm making the case that mandatory unpaid overtime is effectively wage theft. It is legal in the US because half of jobs there are "exempt" from the usual overtime protections. There's no ethical reason for that, just political ones.

At any rate, I think people who want to crack down on meal expenses out of a sense of justice should get at least as annoyed by employers taking advantage of their employees in technically allowed ways.

Note that employers do this as well. A classic one is a manager setting a deadline that requires extreme crunches by employees. They're not necessarily compensating anyone more for that. Are the managers within their rights? Technically. The employees could quit. But they're shaving hours, days, and years off of employees without paying for it.

JIRA has a notion of business value points, and you could make up similar metrics in other project planning tools. The problem would then be how to estimate the value of implementing 0.01% of the technology of a product that doesn't sell as a standalone feature. If you can accurately do that, you might be the 100x employee already.

The main problem is that too many C++ engineers don't do any of that. They have some sort of learned helplessness when it comes to tooling. Rust for now seems to have core engineers in place that will do this sort of on behalf of everyone else. Language design aside, if it can find a way to sustain that kind of solid engineering, it will be hard to argue against.

I'd rather keep the dysfunction of national politics away from my kids' food, personally. At least I can reasonably move if local dysfunction goes past tolerable levels.

The simpler and more convincing explanation is that lawmakers write bad laws, regulators write bad regulations, and everyone votes on hot button issues like the economy, immigration, and trans athletes in sports. School lunch policy details don't get enough attention.

Set medium term goals. Don't try to lose 20 kilos in six months. Lose the next kilo by this time in two weeks. Similarly, don't try to lose 0.1 kilos by tomorrow. Weight naturally fluctuates day to day based on water intake, sodium intake, muscle fatigue, and other things. But in the range of 2-3 weeks, you should be able to lose enough weight to see signal in the noise of day to day fluctuations.

If you aren't hitting your medium term goals, find a way to cut calories more. Starting the first month doing a comprehensive calorie log is valuable to help calibrate what foods and portion sizes are relatively problematic.

The rest is just finding eating patterns that work for you that help keep calorie levels low enough. There's a lot of advice about ways to do that, and most need to be taken with a grain of salt, but it's probably true that you can min/max at the margins by increasing fiber intake, increasing protein intake, drinking more water, eating more raw plants, intermittent fasting, and that sort of thing. But you'll mostly see fractional improvements on top of the bottom line math: calories burned need to exceed calories consumed.

As noted elsewhere here, it's a lot of exercise to burn off a few pieces of bacon. Exercise is good for weight loss, but again, it's mostly at the margins for the average person, especially if that person is not an athlete.

The difference in build times between identical code compiled with the C language or C++ language is probably negligible. Or at least dwarfed by using a better build system, a faster build machine, and/or some sort of build caching technology.

> Beyond that, there is no compiler flag to stop requiring explicit casts of void pointers before assigning them.

I believe that's true. And there are probably a few other ergonomic differences beyond this one. Has anyone proposed that as a feature flag for Clang and/or GCC? Open source C and C++ compiler devs don't have a lot of free time such that they peruse social media looking for things to do.

No comment on your anecdote other than to say I have heard versions of that story before but with other programs and in basically every other language. Including C.

I'm not saying you're wrong. I think a lot of your points are valid points. About taste. Which is fair and fine, but it's also true that the difference between C and C-style C++ are pretty minor, especially if someone knows how to enforce coding standards with clang-query wired up to CI or something like that.

I would expect it's at least slightly better for morale, recruiting, and retention. I also expect that executives and middle managers move to use these as an opportunity to reinforce corporate values, whatever that means to them.