Yeah, that's one of my ongoing frustrations as a maintainer :) I've always gone straight to a tool's docs when I want to start learning it. I look for other sources, too, but I start with the docs, and I always assumed other people did, too. That's definitely not the case - many people deliberately _don't_ look at docs [0].
I definitely don't expect everyone with an existing Redux codebase to know that RTK exists already (although sure, I'd love to wave a magic wand and update every Redux codebase to RTK overnight). But it is sad to see new tutorials being posted that A) don't teach anything new compared to the plethora of existing tutorials, and B) continue to teach older patterns that are the same things people have complained about Redux over the years.
So, even though I'm spending a lot of time updating our docs and highlighting RTK as the default way to use Redux, many people just rely on whatever other courses and tutorials they've looked at for their knowledge.
I definitely don't expect everyone with an existing Redux codebase to know that RTK exists already (although sure, I'd love to wave a magic wand and update every Redux codebase to RTK overnight). But it is sad to see new tutorials being posted that A) don't teach anything new compared to the plethora of existing tutorials, and B) continue to teach older patterns that are the same things people have complained about Redux over the years.
So, even though I'm spending a lot of time updating our docs and highlighting RTK as the default way to use Redux, many people just rely on whatever other courses and tutorials they've looked at for their knowledge.
[0] https://twitter.com/acemarke/status/1213898963679633411