Bonum Certa Men Certa

Computing Fundamentals

2020 figosdev

Index



IBM vs Core
Chapter 7: Computing Fundamentals



Summary: "A graphical interface is better, for some things -- sometimes. But it will also put a lot more on our plates."

Ask people to explain computing in as few words as possible, and many will start telling you about 1s and 0s. They're not wrong, binary computing is very useful and quite relevant in our modern world of tiny silicon-based switches.



But if you want to understand the fundamentals of computing, 1 and 0 doesn't tell you very much. A few computers, like the Harwell-Dekatron WITCH, even processed or stored numbers in base 10 like we normally do on paper. But what are these numbers doing?

"A few computers, like the Harwell-Dekatron WITCH, even processed or stored numbers in base 10 like we normally do on paper."As mentioned in the first chapter, modern computers evolved from automatic calculators. Creating a program is really telling the machine to move numeric values into certain places.

At the most fundamental level -- where I never do much of anything and a "low-level" coder could tell you far more, you are working exclusively with numeric codes for everything.

If that sounds incredibly tedious, it is. The main thing that people do on this level (called "machine code") is find ways to make coding easier.

In the very early days (the 1960s were futuristic by comparison) when someone wanted to use a computer, they would do all of it in numeric machine code, or they would punch data into cards that helped correspond single-character codes with numeric (consecutive) physical positions that the computer could read with a card reader.

These numeric codes went into "dictionaries" or paper code books. After some months or so, you might find that you had a dictionary with several useful computer "routines" in it.

"The difference between an interpreter and a compiler is a like the difference between hiring a personal translator and commissioning a translated work."The goal of making these hand-coded dictionaries into automatic programs became the basis for the first compiler. Like the BASIC interpreter in chapter 2, the job of a compiler is to translate codes that are friendlier to a human into numeric codes the computer understands.

This was a revolution for most of us, and while it started in the 1950s, by 1964 this revolution was exactly what made a beginner friendly computer language like BASIC possible.

Now instead of coding the letters H-E-L-L-O (SPACE) W-O-R-L-D into numeric ASCII codes (or Baudot teletype code, since ASCII didn't exist until around the same time BASIC did) and then entering the code to move the numeric data somewhere that it can be output to the screen, you just say:

    10 PRINT "HELLO WORLD"


And run the program. Seems like a lot of trouble just to say two words, but before that it was a lot worse!

If you have followed along and actually installed Core on your "thought experiment" PC, you can run a single line of code very similar to the above line. Just type:

    echo Hello World


It will do exactly the same thing, only this command is for a 1970s-UNIX-style "shell" interpreter, rather than 1964 BASIC.

The difference between an interpreter and a compiler is a like the difference between hiring a personal translator and commissioning a translated work.

"The general rule is that compiled programs are better for tasks where speed is very important, but interpreted tasks are better for code that is going to be constantly tweaked."If you are talking to other people, and have a translator with you, the translator will do the "interpreting" for you as other people talk. Every time you run an interpreted program, you need to run the translation program.

While this has certain costs in terms of efficiency, it means that when you want to change something, you don't have to wait for it to translate the entire program again -- you can just start running the new version of the code immediately.

A compiler on the other hand, translates the entire program into computer-ready instructions. Whenever you run the compiled program, it will run without being compiled again -- but every time you change something you have to wait for the entire thing to compile.

"When you first run Core, it’s not obvious whether the thing you’re using is more sophisticated than the chip from the early 80s running BASIC on the C64."The general rule is that compiled programs are better for tasks where speed is very important, but interpreted tasks are better for code that is going to be constantly tweaked.

Many, though not all of the friendlier languages are interpreted, because it is easier to find and fix problems with shorter waits (or more complicated processes) between edits.

When you first run Core, it's not obvious whether the thing you're using is more sophisticated than the chip from the early 80s running BASIC on the C64. That's because all it gives you for an interface is text on a screen.

If you're used to fancy rectangles with animation and even video, you might look at a simple command prompt and wonder if this is just a throwback to the 70s. But this is an old cover on a much newer book.

Someone who has only used DOS or a C64 can marvel at everything Core has behind the prompt. With a single command you can download a file or a webpage from the Internet.

It might not be available with Core, but with Tiny Core or CorePlus you can play your MP3 files from the command line. And you can run Python, which is more advanced than pretty much any BASIC interpreter or compiler, ever.

"It might not be available with Core, but with Tiny Core or CorePlus you can play your MP3 files from the command line. And you can run Python, which is more advanced than pretty much any BASIC interpreter or compiler, ever."What's more, you can make it do these things automatically, in response to certain events or specific times -- you can even make it do these things in the "background", so that you can keep working or have it do more than one task at the same time.

Sure, you can do all of those things with a graphical system as well. And you need a lot more code to make that happen -- and lots more code means lots more opportunities for large projects to go wrong.

Apart from being a geek's canvas, the command line is also where you go if some parts of the system (like all that graphical stuff people run on top of the OS) aren't working properly. You can fix a number of things from the command line; it's a bit like opening the bonnet of your car.

"Apart from being a geek's canvas, the command line is also where you go if some parts of the system (like all that graphical stuff people run on top of the OS) aren't working properly."But the best part about the command line is that it's faster and easier to write code for. Nearly all frameworks for graphical tools add considerable overhead in terms of resources and code you must tend to.

When you talk to a voice assistant, you're doing something very similar to using the command line.

Selecting things from a series of menus can get tedious when you know the things you want. Imagine if instead of telling someone "I'd like the chef salad" your only choice was to open the menu, find the salad you wanted, and point to it -- and you had to order everything else that way too. When people order fast food, having a menu in front of them often slows them down.

If you had to order that way every day, or for 20 people, you would really start to hate flipping past page after page after page after page, poking at every item with your finger. Sometimes menus help with unfamiliar tasks. Then again, they had menus for the command line as well:

    1. Run Tetris



2. Run Word Processor

3. Quit


It isn't the point of this chapter, but you could -- with only things available to you from Core, code a little menu that displayed a list like the one here, using numbers to run each relevant command, with a number (or letter) that could tell the menu to quit.

Sometimes, instead of creating a menu, the easier thing to do is just take a command that already exists and giving it a name you prefer.

If you like the editor that's called "nano" but just want to say "edit" or even "e" (why not both? You can do both if you want) you can create a second command so that whenever you hit the letter "e" and then hit enter, it will run nano. That's even less work than hunting through icons on the desktop. Setting this up is also less work than creating a menu.

"A graphical interface is better, for some things -- sometimes. But it will also put a lot more on our plates."You can do far more than that, but menus are nice and easy. Shortcuts are nice and easy. Graphical environments can hide a lot of complexity, but they introduce even more of it in the process.

I'm using a graphical environment to type this -- in a window next to another window, in a text editor I helped create -- but did very little of the actual coding for.

And I'm running it in CorePlus. So don't think I'm "fundamentally" against graphical environments or anything. A graphical interface is better, for some things -- sometimes. But it will also put a lot more on our plates.

Licence: Creative Commons CC0 1.0 (public domain)

Recent Techrights' Posts

Datamation, Where I Used to Publish Articles, Appears to Have Been Sold to TechnologyAdvice Only to Become a Slopfarm
I'd prefer to not associate with that site anymore
 
TikTok is Not Harmless (Being CheeTok in the US Will Advance Orange Agenda)
Social control media isn't "fun and games"; it's a digital weapon that lets hostile groups or nations infiltrate others, then turn them against themselves
Andy Farnell and Helen Plews Explain What "Modern" Tech Does to Old People
Imposing terrible tech "religion" on people is not helping them
Tomorrow the Free Software Foundation (FSF) Turns 40 and Its Web Site is Still Slow Due to DDoS by LLM Slop Bots
For an advocacy group, uptime is important (for its message to remain accessible)
Slopwatch: Google News as a Firehose of LLM Slop About "Linux"
Google News is really bad
Links 03/10/2025: "NPR’s Economics Lessons Come With Neoliberal Spin" and Canada Post at Risk
Links for the day
Gemini Links 03/10/2025: Panic Attacks and Food Adulteration
Links for the day
Links 03/10/2025: Lawyers Caught Using LLM Slop Explain Why They Did It, LibreSSL 4.1.1 and 4.0.1 Released
Links for the day
FSF Board Grew 50% Since Last Year, Has New President, Turns 40 in Two Days
It's a good move for the FSF and - by extension - for software freedom
Links 03/10/2025: Conflicts, Death of TypePad, and TikTok/CheeTok Gives a Boost to Far Right Groups in Europe
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, October 02, 2025
IRC logs for Thursday, October 02, 2025
Slopwatch: Linux Journal, Google News, and LinuxSecurity
They carry on polluting the Web with fake articles
Gemini Links 02/10/2025: Kubernetes With FreeBSD and robots.txt
Links for the day
Links 02/10/2025: 'Open' 'AI' Resorting to Gimmicks and Fake Funding, Europe’s ‘Drone Wall’ Discussed
Links for the day
Links 02/10/2025: Brave Passes 100M Users Milestone, Kodak Selling Its Own Film Again
Links for the day
Michael “Monty” Widenius: It Started in 1983 With Richard Stallman (RMS)
The other co-founder of MySQL is a bit notorious for confronting RMS rather viciously
For the Second Time in a Few Weeks Microsoft Lunduke Makes False Accusations Against Senior Red Hat Staff to Incite a Despicable 'Troll Army'
Nothing that Microsoft Lunduke claims of says can be trusted
su lisa && rm -rf /home/ibm/power
Novell was ruined by another person from IBM, Ronald Hovsepian
A Record Demand at Microsoft: Demand to Cancel
What we're witnessing is a very ungraceful destruction of XBox
Microsoft is Losing Europe
Hence all the "support" and "discount" offers that are limited to Europe
The Free Software Foundation Starts Fund-raising for 40th Anniversary
New pop-up 2-3 days ahead of the 40th anniversary event
Systemd Breaks Networking in Debian and Microsoft Staff Rushes to Make Face-Saving Excuses in LWN
Microsoft's bluca is already there in the comments, his Microsoft money pays for LWN to let him leave comments early
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, October 01, 2025
IRC logs for Wednesday, October 01, 2025
What the End of XBox Will Look Like: a Fiery Crash
XBox is the next Skype. It won't last much longer. Expect many more layoffs.
Richard Stallman is Going to Finland to Give a Talk Next Thursday
A day later he speaks in Sweden
Gemini Links 02/10/2025: SMTP Pipelining and End of ROOPHLOCH 2025
Links for the day
Slopwatch: Plagiarism, Fake Articles, and FUD About Linux
not a day goes by without Google News feeding FUD from slopfarms
Gemini Links 01/10/2025: Chat Control and End of Life
Links for the day
Links 01/10/2025: Long Covid Risk Reiterated, "Bitcoin Queen" Caught
Links for the day
Links 01/10/2025: EA $55 Billion Deal is Debt and Slop "Raises Vishing Risks"
Links for the day
Bluewashing at Red Hat Means Redundancies
The man who sold Red Hat to IBM meanwhile became a Microsoft Mono booster
After Killing OpenSource.com, IBM ('Red Hat') and OSI Told Us OpenSource.net Would Replace It (But That Didn't Happen)
Now it's time to move on, perhaps tarnishing the "Open Source" label some more (for whatever sponsor wants this)
Linux is Not a Community Project, It's a Wall Street Product
The core goal should be freedom
Bad Actors Abusing the Free Software Community, Vandalising It Using Rogue Politics and Old Tactics
Oil giants have long attempted to do this; now, the digital equivalent of Big Oil does this in technology
Social Control Media Isn't the Future, The Federation or Fediverse Isn't Growing, People's Accounts Vanish for Good
users' accounts will get deleted, not just become inactive
IBM is Failing, This Helps Show Wall Street is Entirely Detached From Actual Commercial Performance
IBM is unable to grow, it's just constantly shrinking
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, September 30, 2025
IRC logs for Tuesday, September 30, 2025
Clerical Aspects of Publishing and Development
In Free software, the management aspects are considerably reduced
Slopwatch: Fake Articles and Google News Promoting "Linux" Spam or Bot-Generated Fear, Uncertainty, Doubt (FUD)
These slopfarms help misplace blame
Third Wave of Microsoft Layoffs in September, This Time Many in Liverpool Affected
Be ready for more waves of layoffs ahead of the so-called "results" in late October