Why unnecessarily add that additional uncertainty?
Put yourself in a beginners shoes, now you have to worry about a resistor.
I regularly do when viewing his videos on setting up software dev environments just like this one.
I'd far rather know I should be putting a resistor in than worry about whether I have a busted GPIO or LED.
How many do I need, what size, type, does it even matter?
Give a value, or a range of possible values, it's really not that hard.
Oh god on eBay they only sell hundreds in a kit, I don't need that many jeez maybe I'll pass on this.
There is value in making a piece of content as accessible and digestible as possible.
If I could do this when I was eleven over 45 years ago, and I could only afford to buy resistors one at a time with pocket money when they were, in today's terms, $2 each, then I'd say that's hardly a chore.
If you look at the other stuff Dave was using, like the breadboard, the Pi GPIO breakout board, and the LED itself, it's quite the stretch to suggest that a resistor is going to be a problem. Furthermore, IME the kits that include these GPIO breakout boards & breadboard also include a selection of LEDs and resistors, including 220 ohm resistors specifically designed to be used for LED current limiting.
Heaven forbid they blow something up and will have to engage with the community or dig deeper into why it didn't work. They might actually learn some troubleshooting too.
You seem to be contradicting yourself. You want it to be "accessible" so they're not put off, but at the same time you want them to "dig deeper".
And when they do engage with the "community" I guarantee that the #1 answer is going to be "Where's your resistor?".
It's fine, really. We don't need to be gatekeeping a hobby.
That's quite a stretch, in anybody's book. If I could figure out that a resistor's needed when I was eleven, and purchase one, then I hardly think it's "gatekeeping".