upvote
I learned to code on my school's BBC Micro. [0]

8-bit. 16KiB of RAM. BASIC as the programming language. 640x256 resolution in 8 colours.

I could make that thing sing in an hour. It was hard to get it to do much, but then the difficulty was the fun thing.

By the time we got to the early 2000s and I could buy something with more RAM, CPU and storage than I could ever reasonably max out for the problems I was interested in at the time, I lost something.

Working within constraints teaches you something, I think. Doing more with less makes you appreciate the "more" you eventually end up with. You develop intuitions and instincts and whole skillsets that others never had to develop. You get an advantage.

I don't think we should be going back to 8-bit days any time soon, but in the context of this post, I want novices to try and build software on an A18 chip, I want learners to be curious enough to build a small word game (Hangman will do at first, but the A18 will let them push way, way past that into the limits of something that starts to feel hard all of a sudden), to develop the intuition of writing code on a system that isn't quite big enough for their ideas. It'll make them thirsty for more, and better at using it when they get it.

[0] https://en.wikipedia.org/wiki/BBC_Micro

reply
> Working within constraints teaches you something, I think.

It absolutely does. But every system has constraints; even when provided with massive resources, humans tend to try things that exceed those resources, as evidenced by Parkinson's Law of data https://en.wikipedia.org/wiki/Parkinson%27s_law

reply
It was worse than you remember. You could have 640x256 in monochrome, or 320x256 with 4 colours, or 160x256 with 16 colours (which IIRC was actually 8 distinct colours plus 8 flashing versions of them).

The game Elite did something extremely evil and clever: it was actually able to switch between modes partway through each frame, so that it could display higher-resolution wireframe graphics in the upper part of the screen and lower-resolution more-colourful stuff for the radar/status display further down.

reply
AlexandertheOk's documentary on Elite and the BBC Micro: https://www.youtube.com/watch?v=lC4YLMLar5I
reply
I hear you, having learned programming on a machine even more constrained by the BBC Micro. But learners today are more likely to "Siri, build me a Hangman app."
reply
I’m waiting for somebody to come and tell us about the time they punched cards by hand, one hole at the time, and then threw coal in the furnace to have the cards interpreted by a steam-powered computer.
reply
Is this close enough? it’s from 1969, I wonder what became of them:

“Tomorrow's World: Nellie the School Computer 15 February 1969 - BBC”

https://www.youtube.com/watch?v=f1DtY42xEOI

reply
Do you have a substantive argument against any points made by parent?
reply
I had a similar experience but with design software (which I pirated at the time since I just didn't have the money to buy stuff from Adobe).

I'd install Photoshop and Illustrator on my shitty computer I put together from spare parts my dad didn't have the use of anymore from his business computers. It was horribly slow, but I kinda made it work slowly.

The thing is that I think this is what made me think a bit differently, since everything was slowed down and took more time than I would want it to, I had to make deliberate decisions on what to add/edit. I still work the same way today to pa point, but that's because I'm both faster, more experienced and the computers have gotten more performant (and because I can afford better devices sure).

When I look at my half-brother and his teenage generation I wonder if they can still have such an experience. The personal devices have gotten better and faster, most things are really convenient and you sometimes even don't have to think a lot to do something also because they're cheap to do... they probably won't have the experience of "grinding it out" just for the sake of producing something they like...maybe sports is the closest...no idea, but have been thinking about this quite a lot recently...

reply
At some point the limitations can flip around.

when you're young, time is infinite, money is scarce.

Older, and time seems to take over. The limitations are - when can you free up the time? Is relaxing allowed?

reply
Oh no argument on that.

I have a typical yuppie software job with decent pay, so generally I will buy the right tools for a job now instead of trying to make due with whatever I can scrap together. I'm not that busy of a person, but I certainly have more obligations than I did when I was sixteen, and now sometimes it really is worth it to spend an extra grand on something than it is to spend a week hacking together something from my existing stuff.

Still, I look back at the hours I spent making terrible YouTube videos with my terrible computer really fondly. I was proud of myself for making things work, I was proud of the little workarounds I found.

I think it's the same reason I love reading about classic computing (80's-90's era). Computers in the 80's were objectively terrible compared to anything we have now, and people still figured out how to squeeze every little bit of juice possible to make really awesome games and programs. The Commodore 64 and Amiga demos are fun to play around with because people will figure out the coolest tricks to make these computers do things that they have no business doing. I mean, the fact that Bad Apple has been "ported" to pretty much everything is something I cannot stop being fascinated by. [1] [2] [3] [4]

[1] https://youtu.be/2vPe452cegU

[2] https://youtu.be/qRdGhHEoj3o

[3] https://youtu.be/OsDy-4L6-tQ

[4] https://youtu.be/Ko9ZA50X71s

reply
It probably depends where you live. When I was young, time was infinite and money were scarce. Now they're both the limit.
reply
It's a great example of going the extra mile due to external limitations. I bet you developed skills and intuitions you wouldn't have if you started with great hardware from the get go.
reply