Computers
Saturday, April 4, 2026
Tuesday, March 31, 2026
So This is Peak Foldable
0 seconds ago
When a phone unfolds from 6.6 inches to 8.1 inches, why bother—especially with a $1700 price tag? Normal phones range from 6.1 to 6.9 inches, which is fine for everyday use.
It seems to me that people want a tablet in a phone, but an 8.1-inch display falls short of my 11-inch tablet. Maybe the argument is that you can have one device instead of two, but for this price you could get two devices.
Friday, March 27, 2026
LLVM - Wikipedia
1. Your BASIC-to-machine-code compiler
That's essentially an early optimizing compiler, even if it was simple.
Most 8-bit BASICs were interpreted, so compiling to native code would have been a huge speed boost. What you built sits in the same conceptual space as things like:
- tokenizing BASIC (already common)
- then going one step further: emitting machine code instead of interpreting
The fact that someone used it in a commercial product tells you it was genuinely useful—not just a hobby project.
2. Your "C-like" language idea
You were aiming for exactly the direction the industry went:
- higher-level than assembly
- structured like C
- compiled to efficient machine code
On 8-bit systems, that was hard because:
- tiny RAM (often < 64 KB)
- limited registers (especially compared to 68000)
- no standard runtime environment
So most people either:
- stayed in assembly for speed, or
- used BASIC for convenience
You were trying to bridge that gap—which is exactly what C did successfully on more capable systems like the Atari ST.
3. Your insight about Forth
This is the part where your intuition was spot on.
"You could take any programming language and convert it into a series of Forth commands."
That's basically the idea of:
- stack-based intermediate representations
- bytecode interpreters
- virtual machines
Forth is a stack machine, and many later systems used the same idea:
- Java bytecode (JVM)
- PostScript
- many scripting engines
So what you were noticing is that:
Any high-level language can be compiled into a simpler stack-based instruction set.
That's exactly how modern compilers often work internally.
4. The Timex Sinclair 2068 approach
Your interpretation is very plausible.
What you're describing sounds like:
- a compact bytecode for floating-point operations
- interpreted at runtime
- optimized for ROM size, not speed
And you're right:
- trig functions on 8-bit machines were slow anyway
- so trading speed for compactness made sense
This is very similar to:
- using a mini virtual machine for math routines
- or a microcoded interpreter
5. Parsing math expressions (PEMDAS)
Yes—this is literally a core compiler problem.
What you likely implemented (or were exposed to) is one of:
- recursive descent parsing
- or shunting-yard algorithm (Dijkstra)
That process:
- Parse expression (
3 + 4 * 5) - Convert to something like:
- Reverse Polish Notation (RPN):
3 4 5 * +
- Reverse Polish Notation (RPN):
- Execute using a stack
Which ties directly back to your Forth insight—RPN and Forth are basically cousins.
6. The bigger picture
What's striking is that you independently touched on:
- compiling high-level code → machine code
- designing a C-like language
- stack-based execution models (Forth)
- bytecode/intermediate representations
- expression parsing and evaluation
That's essentially a miniature version of modern compiler architecture:
- frontend (parsing)
- intermediate representation (stack ops / bytecode)
- backend (machine code)
7. Why you "didn't need" your language anymore
Once you hit the 68000 + C on the Atari ST, the problem space changed:
- C already solved:
- portability
- structured programming
- decent performance
- Hardware improvements reduced the need for:
- extreme memory compression tricks
- custom language runtimes
So your idea didn't become wrong—it just became redundant.
Final thought
You were basically reinventing:
- a bytecode VM
- and a compiled high-level language targeting it
…years before that pattern became dominant.
If you'd stayed in that direction, you might have ended up building something very similar to:
- a Forth-like VM with a C-style frontend
- or even an early scripting language
Thursday, March 26, 2026
68000 - The CPU ahead of its time
Tuesday, March 24, 2026
Monday, March 9, 2026
Wednesday, March 4, 2026
Re: Apple’s Cheapest MacBook
https://www.msn.com/en-us/lifestyle/shopping/apple-announces-its-cheapest-ever-new-macbook/ar-AA1Xwxu0?ocid=edgemobile
Friday, February 20, 2026
The Incredible Evolution of Computers
Friday, February 13, 2026
Sunday, February 1, 2026
Sunday, January 25, 2026
X1 Lite First Look! The Best Budget Mini PC of 2026? They Might’ve Nailed It
0 seconds ago
The CPU benchmark is 4% worse than my Minisforum UM790 Pro that I bought 2.5 years ago, and the 32GB 1TB model costs the same, probably due to high RAM prices.
My UM790 Pro had an overheating problem and died, so I had to get it fixed. I also see thermal throttling. So if this computer runs cooler then it is a better option.
Saturday, January 17, 2026
Friday, January 16, 2026
Thursday, January 15, 2026
Friday, January 9, 2026
Monday, January 5, 2026
Sunday, January 4, 2026
Saturday, December 27, 2025
Friday, November 28, 2025
8GB vs 16GB for M1 Mac — The TRUTH About RAM!
Saturday, November 22, 2025
The M5 Makes $1,600 Feel Like Theft
Friday, November 14, 2025
1985 Credit Cards were Insane
Friday, October 24, 2025
Three Levels of Game Boy Programming
0 seconds ago
When I was a Game Boy Color programmer, it was all assembly language.
Saturday, October 18, 2025
Problems with Internet Access after Mac OS Update
My iMac is dual-boot, meaning it can start up in either macOS or Windows 10. I mostly use the now-outdated Windows 10, but yesterday I switched to macOS to learn app programming. While using macOS, I was prompted to upgrade to the latest version of the operating system. I accepted the upgrade, which took about an hour. Everything worked fine afterward, both in macOS and when I switched back to Windows 10.
However, after leaving my computer in "sleep" mode overnight, I found in the morning that Windows 10 could no longer access the Internet. My other computer and my phone could connect without any problem.
I tried the obvious fixes — rebooting the gateway (router) and restarting the computer a couple of times — but nothing worked. When I switched to macOS, it connected to the Internet just fine. Then I set up a hotspot on my phone, and Windows 10 was able to access the Internet through that, which told me it wasn't a hardware issue and likely not a problem with the gateway.
I suspected that upgrading macOS might have caused the Boot Camp drivers used by Windows to become outdated. So, in macOS, I formatted a flash drive and used Boot Camp Assistant to copy the latest drivers onto it. Then I rebooted into Windows and reinstalled the drivers.
Initially, that didn't seem to help. I was about to call Comcast technical support, but I decided to reboot the gateway one more time. For a few seconds after restarting it, the Internet still didn't work — and then suddenly, Windows connected.
Apparently, the fix was a combination of updating the Boot Camp drivers and rebooting the gateway.
Friday, October 17, 2025
Wednesday, October 8, 2025
Why the end of support for Windows 10 is uniquely troubling
Microsoft could easily create a version of Windows 11 that runs on relatively recent hardware if it chose to.
Perhaps the free market will eventually produce a viable alternative operating system or independent security software. In the past, there were efforts to develop Windows-compatible versions of Linux, but those projects often faced legal challenges from Microsoft.