There are valid arguments to be made about object-oriented programming not being a hammer fit for every nail, particularly in regards to game programming. It's easy to caught up in a trap of organically forcing too much hierarchy and structure onto a project while still in the planning stages. You can tell the awkward, haphazard results of an OOP library that was built on the principle of "whatever the developer thought was a good idea at the time" versus one that was actually engineered - it's the difference between reading a novel in the latter case and a rambling screed in the former.

Unfortunately, I think Casey tends to take his dislike for OOP a bit far, and rather than arguing against using OOP badly, or using it where it isn't really the best option, he seems to reject it in its entirety. There are situations in which it works, and ways to make it work well.

Watching the handmade hero stream archives on youtube, i find it useful to read the comments (one of the few times you should read the comments on youtube) where clearly intelligent and competent programmers call him out on his curmudgeonly bs time and again.

Of course, he's a much better programmer than I am, and he has shipped a game and I have not, so I will listen to most of what he has to say, but when things like const being useless come up I just have to roll my eyes.

I think that this is less a "movement" and more a "group of people unable to take Casey Muratori's personal opinions with the necessary grain of salt."