I obviously don't know your kid, but I doubt that aptitude/ability is going to be a blocker from getting simple Scratch programs running. I know several others who've run classes to a wide range of ages and abilities and not one of the kids has failed to get to grips with the basics.
I can accept that attitude/interest (wanting to consume rather than produce) is going to be an issue for some children, but that's always been the case. And no matter how easy or hard it is to make things, those children aren't going to want to program.
My point was less about Scratch specifically - there's a few similarish programs out there that can be used instead. It's more that the incentive to learn and availability of distractions hasn't really changed in the 30 years since I was a kid, and if anything the barriers to getting into some form of programming have dropped drastically since those days.
As your parent suggested, not everyone who had computers back than had or felt the need to program them.
1) It was hard to distribute his creations
2) Lack of natural aptitude / ability
3) Too easy to consume without producing
We had a little more success with Construct 2. The main difference being that the games could be distributed to an iPad or any other HTML 5 web browser effortlessly. Maybe Scratch addressed that already in the 18 months since we've used it?