And are very often right about it. Delivering monoliths can require such amount of bureaucracy and needless coordination that it slows everything down. I've seen it.

> Inexperienced developers proposing microservices because they think it sounds much more fun than working on the system as it is currently designed.

It doesn't matter who proposes something, if its good idea, do it. And in my experience it is indeed more fun (in addition to other benefits).

> Technology does not solve these problems.

Using microservices is a matter of organisation, it has nothing to do with technology. It is non-technical solution for non-technical problem. Any effect it may have on a technology is secondary to main goal.

> In the end, it's absolutely the case that a movement to microservices is something that should be evolutionary

Nothing you said before contradicts that.

> and in direct need to technical requirements

How people are organized is not a technical requirement.

> For nearly every company out there, a horizontally-scaled monolith will be much simpler to maintain and extend than some web of services,

To maintain, yes. To develop, often not.