I don't think there is much vision or editorial control. Anyone with an idea can seemingly produce content for these platforms and it almost always falls short.
How do you position this video content versus documentation? Anecdotally, younger audiences may have a preference at times, but I think it's more about the use case and preparation. I've seen really good video content and bad. Same applies to docs, or any content.
I mean IME with Pluralsight, I fully meant what I said. Most videos barely go beyond the documentation.
I've paid for Lynda (now LinkedIn learning), Frontend Masters, Egghead, educative.io, Udacity, Laracasts, UI.dev, Safari, Ardan Labs, etc.
If you want to interview for a FAANG job, educative.io has the best content. Everything else on the site is extremely poor but hey if you need to refresh on system design or leetcode patterns no other content is as good.
I use to like Frontend Masters, but the decay rate of their courses is too high. You can take a workshop from 2 months ago but the instructor will never mention the version of the language they use and often the project files will fail to install. I absolutely do not think this is a good thing and should absolutely not be tolerated. You can blame NodeJS but it's a terrible indictment when 90% of your catalog is worthless. I've also disliked the new generation of instructors they have where it's mostly the same 3-4 people every year that always talk about the same topics. It's disappointing because this would be a service I use to recommend every frontend dev 3 years ago.
The only thing I continued to subscribe to is Safari/O'Reilly. Here you get books from all the major publishers and some decent courses as well (like Ultimate Go by Bill Kennedy); but I won't be renewing this. Books on extremely advance topics aren't released in massive amounts annually. There's like maybe one or two software books truly worth buying every year. Here's what I've bought the last 5 years (Beautiful Code, The Cathedral & the Bazaar, The Soul of a New Machine, Writing An Interpreter In Go, Game Engine Black Book, Refactoring UI).
Maybe I've progressed enough in my career that I see the best way to learn is to just read the docs ASAP then just build as many things as possible after. I truly mean build too, you can't watch someone make a project for you and copy them. You have to struggle when learning, because that's how you confirm your priors and what you actually know. There's also the benefit of just getting better at delivering software the more you make.
They've done studies about pottery classes where two groups of students were graded differently, one would be graded on the amount of pottery they make and the other would be graded on a single piece at the end of the system. The students that were graded on the amount of pottery tended to do better and make more advance things. This mimics my experience as a dev too.
How do you position this video content versus documentation? Anecdotally, younger audiences may have a preference at times, but I think it's more about the use case and preparation. I've seen really good video content and bad. Same applies to docs, or any content.