The problem is that's not really how people get started. Hello world is how you get started in a university intro course, not in your parents' basement.

What happens there is that you have a pile of photos that are all in one folder and you want to organize them into separate folders by date. A problem you're actually having, not a homework assignment. Which is possible to do automatically, because they all have metadata with that information in it. So you find a python script somebody wrote to do that, and it works! Then you realize the script is just a text file and you can modify it to sort using geotags or something else instead, and now you're down the rabbit hole. But only if it's easy to see and modify the code that runs on the device you actually use.

Not everyone learns the same way or for the same reasons.

For example, I learned to read at the same time I learn to code, and from the same source — I had the unusual combination of not just the right birth year, but well-off parents and two elder siblings that had gotten bored of their Commodore 64 just as I was reaching reading age.

Back then my coding was, naturally, 95% transcribing from the manual, but it was fun. One of the few ones I can remember reasonably well this far removed from the experience was a sentence generator that had a list of nouns, verbs, etc and picked from them to build grammatically correct gibberish.

Hello world is how a lot of us started in C with the K&R book, wherever we were. Most of us didn't want to organize photo folders, we wanted to make the computer display something cool or play a song or something, and usually we had to start with something elementary when tackling a new language, especially a complicated one like C.

I can still remember being 11 years old and meticulously keying in the hello world program on my dad's aging Tandy Model 16, then saying 'cc hello.c' and watching as the compiler chugged through the tiny program for a minute or two. (It #includes stdio.h, so there was more code to go through than it seemed, plus there was a linking step. And not much actually happened, because Unix C compilers are silent if there are no errors.)

When I ran a.out and saw "hello world" appear, I was over the moon. It was like clearing 1-1 in Super Mario Bros. for the first time. Like I had surmounted the first obstacle and was thus ready for all the challenges that lay ahead.

I don't know why a raspberry pi is supposed to be a good device to learn programming other than the fact that it forces you to use Linux. Do kids really ssh into their raspberry pi from their phones? Or do they really buy an expensive screen, expensive cases and expensive peripherals adding up to $200?

I also doubt that raspberry pis are actually the type of device that schools are interested in. What they'd want is the TI-84 equivalent of a laptop. It should be easy to reset the laptop to factory conditions and it would only run a few specific preinstalled programs (one of which would be a barebones IDE, probably for Java). To me it feels like the raspberry pi fails at all of these. You have to mess with hardware and then mess with the software. A school provided Chromebook with student accounts managed by the school would be way more practical.

However, if you actually want people to learn programming organically, it's much simpler to just get a Windows laptop and use that as the main device.

I too have doubts about the real-world suitability of the Raspberry Pi in formal education environments, but certainly the business of resetting it _is_ a solved problem; every kid is issued their own SD card, and can flash it back to the starting image whenever they want.

It all depends on what you want to learn.

On a RPi, with a standard laptop on the side (Windows/Mac/Linux, doesn't matter), and some basic installed tools, you can pull down and configure Alpine Linux and run a bare bones IoT Linux platform. If you want to get really gritty, you also configure and build U-Boot as a primary loader.

Once you get passed that point, you pull docker into your Alpine build and start running containers.

Stepping through that full process will teach you research (because you are going to be reading a lot about how to pull that off), it will teach you about Linux kernel configuration. It will teach you to be at least comfortable with git.

There is a lot you can learn on a Raspberry Pi, cheaply, that only involves plugging in an ethernet port and power supply, and never seeing anything on a terminal.