Live data from Hacker News

Childhood Computing

susam.net

41–50 of 133 posts

Re: Childhood Computing

#41
Some of my fondest memories as a young kid was hacking away at an 800mhz machine my dad bought me. Certainly a lot of time was wasted, but my knowledge of the system was also helped a bit.

Seeing kids nowadays interfacing with just a touch screen makes me fearful that a foundation of knowledge is not being built, even among the more nerdy types.

Re: Childhood Computing

#43
post #8

I never understood why Microsoft didn't have affordable licences to encourage kids to program. The school computer lab had Visual Basic but you only got an hour week in there as part of the computing subject, the school library computers couldn't have it because the licence was per seat not per site. You really only had QBASIC which was great but we really wanted to write Windows apps. You'd be up for a thousand doll…

People forget how locked down the systems were until Borland and finally GNU gcc entered the market (Unless you went Masm or Pascal.) I remember the MS visual C++ and VB manuals with compilers were over $8k/seat at one point (would be almost twice that in today dollars).

People sometimes underestimate how important search engines are to build applications without official documentation.

Supporting FOSS is more than a convenience for some, as most remember locked ecosystems were not fun at any age. I remember GW-Basic and VB3.0 made building programs easy for kids, but it had other issues besides the license cost. Prior to Visual studio, making standalone binaries was simply too difficult for most until the Internet.

Now the average AAA game is around 40GiB on Steam, and g++/clang is the standard tool-suites. Fun times, =3

Re: Childhood Computing

#44

At school we had a bunch of older machines with windows 3.1, which had some touch typing program installed - it was the only thing we were allowed to use Our first family computer was bought back in 1995. IIRC it was a 166 MHz Pentium / 16 MB ram machine with Windows 95. It cost around $3500-4000 back then, and that's not adjusted for inflation. EDIT: As a side note, 3 years later I managed to get my hands on a copy…

I once discovered where the texts for our touch typing exams were saved on the network.

Made for some funny exams afterwards...

Edit: well, funny for my adolescent self...

Re: Childhood Computing

#46
post #8

I never understood why Microsoft didn't have affordable licences to encourage kids to program. The school computer lab had Visual Basic but you only got an hour week in there as part of the computing subject, the school library computers couldn't have it because the licence was per seat not per site. You really only had QBASIC which was great but we really wanted to write Windows apps. You'd be up for a thousand doll…

...because Sales is busy with bombing schools with CoPilot & MS365 subscriptions and Sales Guys does not have this in their crosshair: They could create a much bigger and earlier addiction to MS products if they would enforce coding-for-kids-activities in schools and colleges :)

Copilot and MS365 have some API areas that no one outside MS actually knows what they do.

Day 2 task was cleaning our Win11 Steam game install drive:

https://www.oo-software.com/en/shutup10

https://github.com/zoicware/RemoveWindowsAI (when it works)

Day 1 task installing Win11 Pro in offline-mode without TPM/Bitlocker speeds up the benchmarks a bit for a game system:

https://github.com/pbatard/rufus/releases

Fun times, but most of the Win experience has always been removing garbage code/adware/shovel-ware. =3

Re: Childhood Computing

#48

I remember playing Digger on my IBM PC clone sold by AT&T (6300) back in 1987 or 1988. I also remember that the game speed was set to some factor of the computer's clock speed. When I later tried to run the same game after I upgraded my hardware, the game went so fast, you could not even play it.

That's where your PC's turbo button comes in!

Re: Childhood Computing

#49
A general thought on children and computers, not directly related, but that I've always wanted to communicate here:

One of my strongest-held opinions is that children need to be taught, explicitly and by example, that there is nothing you see on the screen that simply "comes with" the computer, and that of all the fascinating/distracting/useful things on the web, none of it just "appeared." It is all the result of people making creative decisions and doing creative, technical, intellectual work to bring ideas to life.

Lots of stimulating books and messaging for children focus on how things in society and in the physical world come to be. Holes are dug, resources are gathered and processed, smart people create complex things including machines that create even more complex things. People perform hard labor to achieve amazing things. People gather, form consensus, and create social structures and government. People have ideas and create art. People observe problems and create solutions.

Children internalize this messaging and develop an appreciation and understanding of how effort, creativity and intelligence result in amazing things that make everyone's lives better, but (in my opinion) that messaging was never sufficiently updated to ensure that that appreciation and understanding extends to software, which increasingly runs our world. We don't put enough effort into showing children that their favorite games, all the stuff in all the menus on our phones, all the software they use to learn or communicate or play, all of it is made by people who had ideas, made design decisions, and then made them real through accumulated wisdom and great intellectual effort.

Not every kid needs to "learn to code", but they should all learn that everything they look at and tap on their screens was made by people who did, and who wanted to make things to solve problems and make life better.

It's unfortunate that the rise of AI slop has complicated this message; that's all I'll say about that.

Re: Childhood Computing

#50
post #28

One thing that was nice about the graphics programming those days was that when you drew something on the screen, it remained there until your program erased it. This means that you could create cool looking graphics easily. For example, you can just compute the points of a circle and draw the points one by one, and in the screen it will show a full circle being drawn. "Modern" graphics libs (even SDL I think), made…

Your post just clicked something from of a deep memory into place.

In the early 80s when the IBM PC hit the scene, Hercules had a graphics card that was amazing and offered better than CGA graphics. I was plinking on it at my dad’s friend’s house, drawing circles and stuff, and on HIS computer the graphics were retained. I had to figure out how to clear the screen, whereas on mine, not having the Hercules card, it wasn’t retained. Never understood what was happening until now.

Post reply on HN