For those of us who grew up in the 8-bit era, this has a lot of appeal since that's how we got engaged. But for most kids today, is this sort of ab initio approach really the right way to go about it? Based on my experience with a few different types of kids/personalities, I'm skeptical. Dropping them into the command line / IDE of any language / environment is likely to leave them both unimpressed and lost. Neither…
Kids have it too easy today, they don't have to work very hard to get decent computing experiences, and its not like they have to do any programming at all to have fun. It is also super easy to get addicted to just consuming all the time. It is quite depressing. My kid is still a toddler, but I think I might put a stripped down CLI-only computer in his room when he reaches 5 so he can at least play with it if he want…
A real computer, by definition is something you can program.
Today you don't just find accessible devices meeting that requirement in the wild.
In the microcomputer era you pressed the power button and you had a REPL prompt.
Today there _is_ a computer hidden somewhere inside you laptop or mobile device, but you need to know where to dig to find it.
In the 80s a newly hatched geek just had to crawl over the beach sand until he reached a device and it was a computer.
Today's kids are surrounded by computers, but they are all deeply embedded in the devices around them.
After hatching, a modern geek needs someone needs to break the husk around their device to get at the computer first.
So your recipe is exactly the recipe for exposing him/her to a computer.