The point was that "republic" simply means "not a monarchy". The state is a "public thing/matter", not a private concern.

Q: Do you smoke after sex?
A: I don't know. I've never checked.

Nah! Just do all the work on the server and ship raw html to the browser.

There's probably too much metal between the cargo hold and the passenger compartment for Bluetooth to work anyway. I think all actual bombs on aircraft (other than the failed shoe bomber) have been triggered by pressure switches at altitude or timers.

So it's not just that they wouldn't be stupid enough, but also that it probably wouldn't be successful even if they were.

I hate it when that happens!

Yeah? So how come he never speaks and has the language comprehension of a 3-year-old?

... on the memory!

About 30 years ago, I worked with a system that would take documentation*, written by engineers, and automatically generate executable code. It worked. But it was pooh, poohed by our CS people. Because of their AI-completeness criteria. But it worked.

Two things killed it off: It was written by a couple of mechanical engineers. Who couldn't possibly understand how to write code (according to our CS people). And when the push came to move everything from *NIX systems to Windows, Microsofts consultants response was to try and rewrite our system requirements to eliminate anything that their products couldn't do.

*Written in something called Simplified English.

The grid has been forced to change faster than the operator would have liked it to in many places, which is a good thing.

In the main, although the Spanish national blackout just over a year ago suggests that maybe it changed too fast. (Hard to use a stronger word than "maybe" because my understanding is that the report on the causes didn't really say anything).

We are a republic for this reason.

No, you are a republic because your founding fathers, probably ascribing James III more power than he really had as a post-Glorious Revolution monarch, decided that head of state should not be a hereditary position.

How did you "just get" something that has yet to be released?

Whitespace is a HUMAN affordance for a HUMAN audience. If you think it looks kinda okay, that's all that's needed.

There's a bit more to it than that: consistent whitespace means that version control diffs contain relevant changes and you don't need to filter out the changes that just remove some spaces from the end of a line. This is also really a human affordance, but while there are humans in the loop either approving changes or needing to understand when something changed, it's a valuable one. And there's a general principle here which is directly relevant to LLM-generated code, which is that until LLMs have minimising the diffs as part of their goals they're going to produce diffs which take a lot of effort for humans to review.

Yep. But what TFS summary seems to be talking about is investment in utility grade renewable generation. Which will help out the big cities and industrial sites. But they won't do squat for the villages miles off the end of the distribution grid.

They do acknowledge that most of the growth is in distributed systems. And that this growth is difficult to measure using the national grid demand. But it looks like they could use more home and village systems as well.

That might be why a feature exists, or maybe even why a particular paid library was chosen instead of another. That doesn't explain why the code is written the way it was, which is the point of documentation. Why the feature exists is the realm of the PRD, not the design doc.