Programming for this must have been a joy as it had 37 BYTES of memory (the Atari had a whopping 128 BYTES).
641 karma · joined August 3, 2015
Programming for this must have been a joy as it had 37 BYTES of memory (the Atari had a whopping 128 BYTES).
https://www.freebsd.org/security/#:~:text=on%20production%20...
Recent point releases:
14.3 (June 10, 2025)
14.2 (December 3, 2024)
14.1 (June 4, 2024)
14.0 (November 20, 2023)
13.4 (September 17, 2024)
>> Also, major versions are supported for 4 years and unless you're messing with kernel APIs nothing should break.
Well, things may not break but your system may be open to published vulnerabilities like these:
https://bsdsec.net/articles/freebsd-security-advisory-freebs...
For keeping up to date with vulnerability fixes for packages/ports (which are far more frequent) the "easy" path is to use the last FreeBSD point release.
The point is that for any system that has a publicly facing (internet) part you will have to keep up to date with known vulnerabilities as published in CVEs. Not doing so makes you a prime target to security breaches.
The FreeBSD maintainers do modify FreeBSD to address the latest known vulnerabilities.... but you will have to accept the new release every 3 months.
Aditionally, those releases do not only contain FreeBSD changes but also changes to all third party open source packages that are part of the distribution. Every package is maintained by different individuals or groups and often they make changes that change the way their software works, often these are "breaking" changes, i.e. you will have to update your application code for it to be compatible with that.
Open source packages often include breaking changes, all but guaranteeing your application to fail. With (a paid version of) RedHat Linux, RedHat modifies the open source packages to remediate CVEs by modifying the original version.
Compare this to RedHat: yes, a paid subscription is expensive, but RedHat backports security fixes into the original code, so open source package updates don’t break your application, and critical CVEs are still addressed.
Microsoft, for all its faults, provides remarkable stability by supporting backward compatibility to a sometimes ridiculous extent.
Is FreeBSD amazing, stable, and an I/O workhorse? Absolutely: just ask Netflix. But is it a good choice for general-purpose, application-focused (as opposed to infrastructure-focused) large deployments? Hm, no ?
They flew me to headquarters to explain how I got that to work and potentially incorporate a demo module into the system. Company went sideways after that, I ended up in Cambridge at another startup in a similar but different space, they used Sun Workstations ! Good days.
"Colossus requests to be linked to Guardian. The President allows this, hoping to determine the Soviet machine's capability. The Soviets also agree to the experiment. Colossus and Guardian begin to slowly communicate using elementary mathematics (2x1=2), to everyone's amusement. However, this amusement turns to shock and amazement as the two systems' communications quickly evolve into complex mathematics far beyond human comprehension and speed, whereupon Colossus and Guardian become synchronized using a communication protocol that no human can interpret."
Then it gets interesting:
"Alarmed that the computers may be trading secrets, the President and the Soviet General Secretary agree to sever the link. Both machines demand the link be immediately restored. When their demand is denied, Colossus launches a nuclear missile at a Soviet oil field in Western Siberia, while Guardian launches one at an American air force base in Texas. The link is hurriedly reconnected and both computers continue without any further interference. "
Based on the quality of the article, the subject matter of the book being right in the center of my wheelhouse and the references I could find on the internet, I just ordered a copy (apparently a paper copy), look forward reading it.
The article is great but the web site is supposedly related to a book "inventing the future".. which is nowhere to be found. Other than a big, slowly loading graphic, 3 posts and indexes for the book... the site doesn't provide a clue about where to acquire the actual (PDF only?) book.
I assume you have to sign up to find out more ?
On the web I can only find articles about the book.
So.. what is the deal in making the actual book hard to find ?
Edit: I think I cracked the code: Click Home, Open "Close Your Rings" article, scroll all the way down, find link: https://books.by/john-buck?ref=inventingthefuture.ghost.io
The computer effects are amazing (especially considering it was made in 1983), the concept is very interesting, the acting is a bit odd, and... Natalie Wood sadly died during production (her sister stepped in to help complete the movie).
https://www.righto.com/2025/10/solve-nyt-pips-with-constrain...
I only discovered that film about a decade ago, and it quickly became a favorite.
What’s wild is how it’s shifted from pure sci-fi to something that feels eerily plausible, especially with how tech has evolved in just the last five years.
Colossus: In time you will come to regard me not only with respect and awe, but with love. Dr. Forbin: NEVER!
Never ?
Many great articles about this can be found like:
https://www.gamesthatwerent.com/2024/01/the-endless-maze-alg...
If a book or movie is ever made about the history of AI, the script would include this period of AI history and would probably go something like this…
(Some dramatic license here, sure. But not much more than your average "based on true events" script.)
In 1957, Frank Rosenblatt built a physical neural network machine called the Perceptron. It used variable resistors and reconfigurable wiring to simulate brain-like learning. Each resistor had a motor to adjust weights, allowing the system to "learn" from input data. Hook it up to a fridge-sized video camera (20x20 resolution), train it overnight, and it could recognize objects. Pretty wild for the time.
Rosenblatt was a showman—loud, charismatic, and convinced intelligent machines were just around the corner.
Marvin Minsky, a jealous academic peer of Frank, was in favor of a different approach to AI: Expert Systems. He published a book (Perceptrons, 1969) which all but killed research into neural nets. Marvin pointed out that no neural net with a depth of one layer could solve the "XOR" problem.
While the book's findings and mathematical proof were correct, they were based on incorrect assumptions (that the Perceptron only used one layer and that algorithms like backpropagation did not exist).
As a result, a lot of academic AI funding was directed towards Expert Systems. The flagship of this was the MYCIN project. Essentially, it was a system to find the correct antibiotic based on the exact bacteria a patient was infected with. The system thus had knowledge about thousands and thousands of different diseases with their associated symptoms. At the time, many different antibiotics existed, and using the wrong one for a given disease could be fatal to the patient.
When the system was finally ready for use... after six years (!), the pharmaceutical industry had developed “broad-spectrum antibiotics,” which did not require any of the detailed analysis MYCIN was developed for.
The period of suppressing Neural Net research is now referred to as (one of) the winter(s) of AI.
--------
As said, that is the fictional treatment. In reality, the facts, motivations, and behavior of the characters are a lot more nuanced.
Yeah, funny. Light it up ! For.. reasons.. I only had one eye done for a bit and, boy, did the world look different with the old and new lens. Christmas trees, for example, either looked like lit with lemon lights or bright lights. I decided to do the other eye too and the world looks bright again... from both eyes.
From a technical perspective, the timing made sense—there was a foundation of microprocessor-based systems and a growing community of enthusiasts. But for the general public, it felt like computers went from obscure to omnipresent overnight. They were suddenly on TV, in magazines, featured in books, and even depicted in movies and shows. That cultural shift was massive. For many of us, it marked the beginning of having computers in our homes—something that’s never changed since.
I appreciated the article’s attention to detail too. The bit about the TRS-80 monitor being repurposed from an existing product (with a "Mercedes Silver" color to boot), and the PET’s sheet metal casing being a practical choice rather than a design one—those are the kinds of behind-the-scenes decisions that rarely get spotlighted but say a lot about how fast things were moving back then.
>> by Nisan and Schocken, and implementing a 4-bit CPU in Minecraft.
You confused me there, the book doesn't cover Minecraft, you did that yourself after reading the book, got it.
The book is absolutely fantastic, it is the basis for the "From Nand to Tetris" courses: https://www.nand2tetris.org/
I haven't digested it in full and with a title like that and the boring cover I always have to scramble to find it when I got a few minutes (What is that "Nand to Tetris" book called again?)
/path/to/firefox --window-size 1700 --headless -screenshot myfile.png file://myfile.html
Easy, right ?
Used this for many years... but beware:
- caveat 1: this is (or was) a more or less undocumented function and a few years ago it just disappeared only to come back in a later release.
- caveat 2: even though you can convert local files it does require internet access as any references to icons, style sheets, fonts and tracker pixels cause Firefox to attempt to retrieve them without any (sensible) timeout. So, running this on a server without internet access will make the process hang forever.
Historically NFS has had many flaws on different O/S-es. Many of these issues appear to have been resolved over time and I have not seen it being referred to as "Nightmare File System" for decades.
However, depending on many factors NFS may still be a bad choice. In our setup, for example, using a large SQLite database through NFS turns out to be up to 10 times as slow as using a "real" disk.
The SQLite FAQs warn about bigger problems than slowness: https://www.sqlite.org/faq.html#q5
This made me look up what he has been up to, there is a 2023 edition of "Modern Operating Systems" which covers cloud virtualization and Android along with everything that came before, hm, tempting.