When programmers see a terminal, they tend to see it in terms of the freedom and flexibility it provides. To everyone else, it looks broken, primitive and weird.

But most modern frameworks and CMS platforms seem to take for granted that everyone moved on from FTP to git ages ago, which isn't the case.

Where precisely within the workflow of blogging do you think the kind of programmer you describe would appreciate using a terminal?

I wasn't talking about blogging specifically, but in general terms, having to use one for updating and deploying.

I could possibly imagine someone writing blog posts in markdown or plaintext and pushing them somewhere, but that would be the edgiest of edge cases, and even then a native app or web form would be more intuitive.

and that's why your suggestion of missing shell involvement is not that much of a great point in this context of Wordpress

I do all my deployments for all of my applications in a shell.

If I were actively writing a blog, it would be administered in the shell as well.

Surely the point was that the shell is unimportant for the vast majority of users, despite some HN missing its power.

Piping stdout to a new blog post, of course.