Being in the government often leads to reduced popularity.

Consider the options:

1. No early election. RN popularity continues to rise, and they take the presidency and parliament in 2027. Result: Complete power for 5 years.
2. Early election. RN wins, and forms a new government. While being the ruling party, they lose in popularity and lose the elections in 2027. Result: limited power for 3 years.

To me it seems quite clear that option 2 is preferable to 1 for Macron.

How is that the implication when there are lots of other explanations, one even given above?

If the target costs more than the missile (including the opportunity cost), and/or the target is a high priority for repairs, it makes sense to target it. It doesn't need to be more complicated than that.

You forget a piece: "Given these observations, these objectives, and this bit of sound reasoning, ..."

Without objectives, no amount of reasoning will tell you what to do. Who sets the objectives?

What a softie. A real dictator would say something like

Everyone is now required to give birth for the glorious motherland, and those that refuse will be shot as traitors.

Just dual-license your software under the TNGPL (Totally Not GPL) license that just so happens to afford the same protections.

Wouldn't static type checking solve most of these issues?

Good question.

The light output would be the same because there is still only one light source. But as you note, some of the "light" would be absorbed by the wall, so the room would be brighter if you had a mirror. Not twice as bright though, because the wall also "reflects" light, otherwise you would not see the wall.

So, would it make sense to have mirror walls to maximize room brightness? Maybe not, because what the walls end up doing is actually scattering the light, meaning light is spread out evenly, wheras with the mirrors you would have some bright areas (corresponding to the lamp) and some darker areas.

Why host it locally in that case, and why host it on a Pi? Seems rather restrictive for that usecase.

You would think so, but int* a, b is actually eqivalent to int* a; int b, so the asterisk actually does go with the name. Writing int* a, *b is inconsistent, so int *a, *b is the way to go.

I feel like the expectation that a developer can do it all is quite harmful. There are not many other disciplines where this is expected, and for good reason.

Maybe it's better to just admit you don't know how to properly architect a solution rather than pretend you do and create an unmaintainable mess. Maybe you shouldn't pretend you know how to do front-end development instead of creating some monstrosity that no user actually uses due to bad UX. Maybe you shouldn't pretend you understand security instead of introducing half a dozen sql injection vectors.

Maybe it's time to admit that the days of the solo developer are over. It may have worked when there was no internet, no security concerns, no concurrency requirements, etc. But we expect, and deserve, better nowadays.

I think the idea is that big-name men will show up to support women and work for equality, not to creep on them.

The biggest problem I see is that you can suddenly become non-compliant just because Hashicorp decides to release a new service (i.e.they start competing with you, rather than the other way). It can be a huge risk for companies.