You are supposed to capture requirements in Given/When/Then form before coding, and they should be written in a way that is independent of the implementation
The complaint seems to be that what happens in practice is "the devs have taken over" the system, so Cucumber just becomes a test automation software
This has led to writing tests in Given/When/Then format which test overly specific elements of the implementation, and are often written after the fact, instead of as a way to capture requirements.
And some other stuff, but that's primarily what I got out of it.
That's what happened in the projects where I used fitnesse, jbehave, cucumber, etc. The users couldn't understand the artifacts and what they're supposed to do, and the tools were highly idiosyncratic. It ended in becoming just yet another hassle for developers.
Whereas using Excel for specification of calculations (by Business Users or Business Analysts) actually brings the business and developers closer together, removing the need for intermediaries. Business Users are very happy using Excel and checking calculations etc. as it tends to be their home environment.
And the reason seems to be that it's requiring us to express ideas in a vastly simplified language. In order to do that, we have to expand a complex idea to many simpler ideas.
That's making us do the job of the compiler! Real high-level languages are rich with many idioms and structures and the compiler then reduces that to simpler ISA.
Given all the examples given, it sounds more like Cucumber is the problem. Having specifications/tests written in the form of given-when-then isn't shown to have any issues. Rather, taking those specs/requirements and disconnecting them from the people who need them is the issue.