Categories
Computers FORTH IBM Programming

The Architecture of the Stack

Back in the early 1980’s when I worked for IBM, I was able to acquire my own IBM PC and experience my own form digital frontierism. Today I really wish I had a logbook at hand with a record of everything I did as my ability to recall those details has faded with age. A couple of those memories that still do remain with me involve two obscure languages: APL and FORTH. And then there was Borland Turbo Pascal.

In those early days of the 1980’s, memory wasn’t an infinite field; it was a precious, finite resource. While most of us were content living with the structured guardrails of BASIC, there was a subset of us drawn to the elegant, stripped-back world of FORTH.

Learning FORTH felt less like coding and more like learning a new way to breathe. It was lean. It was efficient. It stripped away the overhead of high-level syntax until it was just you, the dictionary, and the stack. There was an honesty to it—no hidden abstractions, just a direct conversation with the hardware.

Then, of course, there was the hurdle of Reverse Polish Notation (RPN). Grokking the stack meant rewiring your brain. You couldn’t just state an operation; you had to prepare the world for it first. You pushed your data onto the stack, one piece at a time, and only then did you call the action. It was a rhythmic, almost percussive way of thinking: Input, input, act.

“In FORTH, you don’t just write programs; you build a language to solve the problem.”

This “bottom-up” philosophy changed the relationship between the creator and the machine. You weren’t just a user; you were an architect of your own vocabulary. To define a new “word” in FORTH was to permanently expand the capabilities of your environment. It was a recursive journey where every small success became a building block for the next complexity.

Looking back, those days with the IBM PC and the stack weren’t just about efficiency. They were about the discipline of clarity. When resources are limited, your thinking must be precise. The difficulty of RPN wasn’t a bug—it was a feature that forced you to understand the flow of data at its most fundamental level.

Categories
AI Audio ChatGPT Computers iPhone Tools

Voice is not what I need…

It’s been a busy week of announcements in tech land what with Microsoft Build, Google I/O, and yesterday’s tease of an announcement by OpenAI and it’s acquisition of Jonny Ive’s company “io”.

Industry pundits are all a Twitter speculating about what kind of device Ive and his team might make to deliver an amazing AI experience to users. Ive seems to regret how “his” iPhone has created such an addiction to screens and seems to want to repent by bringing us something new and “better”. For more, see this tweet: https://x.com/mingchikuo/status/1925543472993321066?s=46

I have one simple request: don’t make voice the primary interface to some new magical device.

I’ve had an iPhone with some serious voice input capabilities for years and the reality is that I rarely use voice. Perhaps if my life was just “bowling alone” I’d find it natural to just talk out loud to a piece of technology. But I’m mostly around other people all day and out of respect for them I simply prefer being silent.

Until some new magical device can capture my thoughts without either voice or keyboard input, I will remain a skeptic. Skeptics like me will reduce the market size opportunity for any such new device. Just sayin’…

Categories
Apple Computers Mac

My First Mac

This week was the 40th anniversary of the announcement of the Apple Macintosh. I still remember the day I got my first Macintosh. It was a Mac SE/30, a compact all-in-one computer with a 9-inch monochrome display. It was the fastest (Motorola 68030 powered) and most powerful of the original black-and-white Macs, and I loved it.

Up until that point I was an IBM PC user having bought my first IBM PC as part of the employee purchase program IBM offered. By the time I got my first Mac I had moved on from IBM and my son had inherited by PC. I remember him being a fan of Borland’s Turbo Pascal on the PC where he really learned programming.

The SE/30 was released in January 1989, and I got mine a few months later at Fry’s in Palo Alto. It came with a 16 MHz 68030 processor, 4 MB of RAM, and an 40 MB hard drive.

The SE/30 was a versatile machine. It had a Processor Direct Slot (PDS) that allowed me to add expansion cards, but I never opted to install any. It could also support up to 128 MB of RAM, which was a huge amount at the time, but it required a ROM swap or a system extension to enable 32-bit addressing.

The SE/30 was my faithful companion for many years. I used it for the usual applications: word processing, spreadsheet, graphics, and games. I also used it to connect to the Internet, using a dial-up modem and a web browser. I was amazed by the amount of information and entertainment that was available online especially on CompuServe where I became a forum sysop responsible for managing several online forums.

The SE/30 was not only a powerful computer, but also a beautiful one. It had a sleek and elegant design, with a platinum-colored case and a friendly smiley face icon on the startup screen. It was easy to use, with a graphical user interface and a mouse. It was also reliable and durable, with no problems needing repairs. I had a carrying case for it and took it on several airplane trips storing it up in the overhead compartment!

The SE/30 was more than just a machine. It was a part of my life during those years. It was my first Macintosh, and it will always have a special place in my heart!