* It's verbose.
* It's not type safe.
* It desperately needs some kind of inheritance - most user stories branch from other user stories (e.g. put product in shopping cart->purchase product) and the only way people who use it can deal with it is by concealing critical details in code or by writing massively repetitive stories.
* What other language has a parser that routinely asks you to write regexes to get things to parse?
None of these things are fixable and the creators have largely reacted to the complaints with gaslighting: "you're just using it wrong".
It can be used effectively if you align the stars correctly but mostly not.
The one thing it does get right is not being turing complete - there's clear value in not using code to describe scenarios.
I wouldn't lump RSpec in with the rest of those.
Spec-style frameworks (like granddaddy RSpec) are terser. They don't have layers of indirection. They're intended to help devs think about how code will be used, not to make code look like English.
Cucumber mostly exists to upsell naive MBAs and project managers on their "pro" tools.
Admittedly, I never dealt with Cucumber.