Childhood Computing

Original Article ↗ Hacker News Discussion ↗

Nostalgic accounts of childhood computing trace how early exposure to machines like the Apple II, C64, Amiga, and DOS PCs—often via school labs or a parent’s work—sparked lifelong careers in programming and IT. Commenters contrast the playful, tinker-friendly environments of BASIC, Logo, and QBasic with today’s locked-down, touch-first devices and commercial ecosystems, arguing that modern children have fewer chances to experiment “under the hood.” Several voices stress the importance of affordable tools, open systems, and explicit education about how software is made so that kids see computers as things they can create with, not just consume.

Nostalgia & Sensory Memory

  • Many recall vivid sensory details: the “new computer” smell, warm circuit boards, dusty labs, PC speaker sounds.
  • Specific machines and eras are remembered fondly: Apple II, TRS-80, C64, Amiga, BBC Micro, VIC-20, Tandy 1000, early Macs, Win3.1/95 labs.
  • Classic software/games recur: Logo, Oregon Trail, Carmen Sandiego, Sierra adventures, Dr. Brain series, DOS shareware, Digger/Dig Dug, QBasic games.

Learning to Program as Kids

  • Common pattern: start with BASIC/Logo/QBasic, then move to Pascal, C/C++, Java, PHP, VB, etc.
  • Key “aha” moments: understanding variables, loops, classes/OOP, and how these unlock the ability to write any kind of program.
  • Many learned by:
    • Typing code from magazines/books and debugging.
    • Viewing HTML source on Geocities/Angelfire and tweaking.
    • Modifying bundled examples like GORILLA.BAS.
  • Early constraints (memory limits, config.sys/autoexec.bat tuning, tape drives) encouraged experimentation and system understanding.

Access, Cost & Inequality

  • Some emphasize luck: having a home PC, well-funded labs, supportive teachers, or parents in tech.
  • Others stress socioeconomic background and parental effort (getting kids into magnet programs) as more decisive than “tinkerability.”
  • High historical tool costs (Visual C++/VB licenses, MSDN subscriptions) are contrasted with free/open compilers (Borland, GCC, Linux) and modern browser-based JS.
  • Debate on how public investment and school policies once enabled social mobility but are perceived as more exclusive now.

Openness, Tinkering & Platform Lockdown

  • Strong concern that modern systems (phones, school-managed devices, locked-down OSes) limit tinkering compared to built-in BASIC-era machines.
  • Raspberry Pi and Linux desktops are seen as partial counterexamples; some criticize UIs like GNOME as disempowering for exploration.
  • Several argue kids should at least learn that all on-screen software is intentionally created by people, not “just there.”

Evolution of Computing Experience

  • Some feel computers became less magical as they grew more powerful, homogeneous, and entertainment-oriented.
  • Nostalgia for retained-mode graphics where drawings persist, and for tight hardware constraints that made clever optimizations necessary.
  • Others note modern high-level tools and abundant docs/search make serious development more accessible, albeit less “bare metal.”

Teaching Kids Today & Screen Debates

  • Parents in the thread wrestle with “no screen” trends vs. wanting to reproduce their own productive tinkering experiences.
  • Proposed compromises: airgapped Linux boxes, retro emulation, and curated environments that avoid addictive platforms while enabling creative play.