Lunduke
Comedy • Gaming • News • Science & Tech
Make Computers Fun Again - Linux, UNIX, Alternative Operating Systems, Computer History, and Retro Computing. Also dad jokes.
Interested? Want to learn more about the community?
January 05, 2023

Why does Linux break everything??
I tried to install Vice to see how to run a C64 and install Vision Basic...but it won't even run!! It installed fine but no runny runny!!
Switched over to my BSD server, which is running just fine, and it runs just fine too! :< Grrr, I blame it on the enssessant update every hour of a rolling release crap schedule....
I'll be moving to BSD shortly!! Can't stand broken things! Linux!! I'm looking at you!!!

Interested? Want to learn more about the community?
What else you may like…
Videos
Podcasts
Posts
Articles
The Lunduke Journal got it wrong about Wikipedia!

Facts are important. When we get them wrong, it must be announced.

Article about the error:
https://lunduke.locals.com/post/5582689/critical-factual-error-found-in-lunduke-journals-coverage-of-wikipedia

Original "Wiki Piggy Bank" article:
https://lunduke.locals.com/post/4458111/the-wiki-piggy-bank

00:14:10
Let's talk about the GNOME Foundation being out of money.

The foundation behind the biggest Linux Desktop environment -- the one used by Red Hat, Ubuntu, & SUSE -- is in dire straights. Wild.

And their only known plan to fix it involves a "Professional Shaman" & "sustainability, diversity, and inclusion". Seriously.

The full article:
https://lunduke.locals.com/post/5572069/is-the-gnome-foundation-going-to-go-bankrupt-in-1-year

00:40:32
Find a Factual Error in The Lunduke Journal articles... I dare ya.

A bunch of articles from The Lunduke Journal, plus contact information, is all right here: http://lunduke.com/

00:10:18
November 22, 2023
The futility of Ad-Blockers

Ads are filling the entirety of the Web -- websites, podcasts, YouTube videos, etc. -- at an increasing rate. Prices for those ad placements are plummeting. Consumers are desperate to use ad-blockers to make the web palatable. Google (and others) are desperate to break and block ad-blockers. All of which results in... more ads and lower pay for creators.

It's a fascinatingly annoying cycle. And there's only one viable way out of it.

Looking for the Podcast RSS feed or other links? Check here:
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

The futility of Ad-Blockers
November 21, 2023
openSUSE says "No Lunduke allowed!"

Those in power with openSUSE make it clear they will not allow me anywhere near anything related to the openSUSE project. Ever. For any reason.

Well, that settles that, then! Guess I won't be contributing to openSUSE! 🤣

Looking for the Podcast RSS feed or other links?
https://lunduke.locals.com/post/4619051/lunduke-journal-link-central-tm

Give the gift of The Lunduke Journal:
https://lunduke.locals.com/post/4898317/give-the-gift-of-the-lunduke-journal

openSUSE says "No Lunduke allowed!"
September 13, 2023
"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044

This episode is free for all to enjoy and share.

Be sure to subscribe here at Lunduke.Locals.com to get all shows & articles (including interviews with other amazing nerds).

"Andreas Kling creator of Serenity OS & Ladybird Web Browser" - Lunduke’s Big Tech Show - September 13th, 2023 - Ep 044
post photo preview

Lucky Rabbit's Foot :)

The Rabbit R1 showed up today. An AI specific device.

First - I really only wanted one thing - a good conversation experience. I like talking to ChatGPT when out for walks, but the voice interface is clunky.

So far - the voice experience is actually quite good. I'm using home wifi, and the speed is very acceptable. The quality of the AI response is also good. It is less "needlessly verbose" than ChatGPT feels.

My first big desire is for explicit and longer context. As long as you are having a back and forth conversation, it remembers very well. Stop for awhile and you start over. How long that while is, I don't know...easily less than an hour.

You can't setup your own custom GPT's. I have one I set up for medical/health conversations with ChatGPT. I explain who I am, my health parameters, my philosophies, who I pay attention to, who I don't (the AHA, ADA, etc.). And every now and then I have it summarize what we've been talking about and add that to the ...

post photo preview
11 hours ago

Should I call them back?

post photo preview
post photo preview
1950s Sci-Fi Style Computers, Powered by a Z80, Built in Holland
Remembering the (very) funky Holborn computers of the early 1980s

Between 1980 and 1983, a little company in The Netherlands built the “Holborn” series of computers… which can best be described as “1950s sci-fi… powered by a Z80”.

Note: The “Holborn” name is to signify that these computers were “Born in Holland”.  Hol.  Born.

While the company only lasted for a few years — and they only produced a handful of models — their distinctive designs (for both their cases and their hardware & software choices) are worthy of being remembered.

Just to give you a good example… this is the Holborn 9100 (and connected terminals):

I mean. Wow! Just look at that monitor! That distinctive neck just screams “1950s futurism”… and I absolutely love it.

Ok. Let’s back up a moment.

The company was founded in Hengelo (a town in The Netherlands, near the German border). This is their first office space:

Pictured below are the founders of the company — Dick Gerdzen (left) and Hans Polak (right) — surrounded by a bunch of Holborn computers and terminals.

Now. The computers. Let’s tackle them in chronological order.

The Holborn 9100

The first computer from Holborn was the 9100 (and the accompanying 9120 terminal). Pictured on the left in the picture below.

Photo Courtesy: Hack42 Museum
 

Note that the 9100 computer portion (where the CPU, drives, etc. were contained) is the size of a mini-fridge or a low profile filing cabinet (with the 9120 terminal sitting on top).

Yeah. The big filing cabinet thing on the floor? That’s the primary computer unit.

The specs of this system were as follows:

  • Zilog Z80 CPU @ 3.5 MHz

  • 72 KB of RAM (expandable to 220 KB)

  • 8 inch floppy drives

Which brings us to the Operating System… it was 100% custom and in-house developed. The Holborn OS was a multi-user system, booted entirely from ROM, which allowed multiple Holborn 9120 terminals to connect to a single Holborn 9100 computer (“Server”).

One extra (and optional) feature of the 9100… it had a photosensitive light pen which could be used as a pointing device. Not a mouse, but a light pen.

What did the Holborn Operating System look like in practice? How did it work? How, exactly, did the light pen work with the included software?

Those are questions I’ve had for many years… yet, despite hunting high and low, have never found so much as a single picture showcasing the Holborn OS in any readable way. Due to the Holborn OS only being available in ROM on the 9100 itself… no known digital archival copy exists.

In the end, only roughly 200 Holborn 9100 units were sold. (Though that number is debated… more on that in a moment.)

The Holborn 7100

This was a simplified (and cheaper) version of the 9100. Instead of supporting a whole office worth of connected terminals (as with the 9100), the 7100 only supported two connected terminals (users) at once.

It looked like the 9100. Acted like the 9100. Just with… less.

It is unknown how well this model sold. It is assumed that it did not sell well.

The Holborn 6100

In 1982, the Holborn Computer company had to make some tough decisions.

Their Holborn OS (booted from ROM), was not proving popular. And the CP/M operating system (from Gary Kildall’s Digital Research in Pacific Grove, California) was rapidly gaining in popularity.

Luckily the architecture already in use by Holborn computers (the Z80) had a native version of CP/M.

Thus the lower priced, and smaller footprint, Holborn 6100 line was born. Same Z80 CPU, and now with a maximum 192 KB of RAM (slightly less than the 9100)… but, this time, booting the CP/M operating system off disk.

No more booting from ROM. No more in-house developed operating system.

This is the Holborn 6140 with the connected 6110 terminal. See? Much smaller than that gigantic 9100 mini-fridge. But still retained that fantastically interesting terminal design.

Here is a shot of the Holborn 6100’s screen, running CP/M.

Image courtesy Technisch museum
 

How many of these machines shipped? Reports put it somewhere in the ballpark of around 100.  Total.

Though the lack of information makes this fact difficult to confirm. Regardless, it was not exactly selling like hotcakes.

The Holborn 6500

The final computer designed by Holborn was the ill-fated 6500.

In the 6500, Holborn removed the keyboard from the terminal body (making it a detached keyboard), and filled the base of the terminal with the computer guts (thus eliminating the need for the separate computer housing used in earlier models). As shown in this advertisement for the “not yet released” 6500:

And here is a shot of the inside of the Holborn 6500, with the top of the case lifted up to show the internals.

Image courtesy: Inexhibit

Unfortunately Holborn Computers declared bankruptcy in April of 1983… before shipping the 6500.

The End of Holborn

And here is where things become increasingly sad for the company.

When Holborn went bankrupt, investigators determined that only 50 units were sold of the 9100 and 7100 combined. And that the company had over 3.5 million guilders in debt. (Guilders were the currency in use in The Netherlands prior to changing to the Euro. Some quick math tells us that 3.5 Million guilders would be roughly equal to $7 Million USD.)

Would the 6500 model have been enough to save the company? Who knows. Considering the poor sales up till then, and the relatively massive debt (when compared to sales), it seems unlikely.

But one thing is for certain… those are some seriously funky (and awesome) looking machines. So I’m sure glad they tried.

If you ever run across a Holborn, count yourself lucky.  These are some of the hardest computers to find nowadays. Considering that only a few hundred were ever sold, you aren’t likely to stumble across them at a flea market or eBay.

With that, I leave you with some pictures of Holborn computers in action.  Because they're just so darned cool looking.

Read full Article
post photo preview
Funny Programming Pictures Part XXXVIII
Go ahead. Call them "memes". I dare ya.

Blah blah blah.  There's too much serious Tech News.  Here's some funny pictures that I definitely did not copy and paste from The Inter-Tubes.

 

Classic.

 

It's funny because CSS is terrible.

 

My favorite part about this is how much I'm crying inside.

 

Around 20 years ago, a fellow Dev Manager and I were interviewing a guy for a senior level programmer job.  We asked him to code a simple function, in C, on the whiteboard.  Something that takes a single parameter and loops on it.  He walked up to the whiteboard and picked up the marker.  At which point you could visibly see -- from the back of his head -- as he had an epic brain fart.  He stood there in silence for a moment, turned around, pale as a ghost, and announced, "I forgot".  He then -- and this was brilliant -- handed me the marker and asked me to do it.  At which point my brain short circuited and I couldn't -- for the life of me -- remember how to do it either.  I start laughing and hand the marker to the other Dev Manager.  He just puts up his hands and shakes his head as if to say, "I can't remember either".  That guy got the job.  True story.

 

WARNING!  WARNING!  UNUSED VARIABLE!  WE'RE ALL GOING TO DIE!

 

I know, I know.  I have issues with this picture too.  I mean.  Seriously.  Rust would obviously be the toilet.

 

Code reviews are just the worst.

 

I don't get it.

 

I'm not saying "Arrays start at 1" is correct... it is merely the only non-insane option.

 

Some of my projects have more commented out lines of code than not.

 

This is correct.

 

By posting this picture, we have accidentally summoned 1,000 Rust programmers.  We're all doomed.

 

Let that be a lesson: Always set an "Out of Office" autoresponce before pushing to production.  Noob.

 

It's has a calculator in it, so this picture is allowed.  You're welcome.

 

Semi-related note: I miss when heavily used compiled code, in CGI-Bin, on webservers.  Those were the days.

 

I like this picture, because it caused me to have 17 contradictory "Well, actually..." responses in the span of 30 seconds.

 

Malloc!  Malloc, like the wind!

 

"I've come here to program with wishy thinking and bubble gum.  And I'm all out of bubble gum."
Read full Article
post photo preview
Critical Factual Error Found in Lunduke Journal's Coverage of Wikipedia!
Facts are important. When we get them wrong, it must be announced.

Stop the presses!  A factual error in reporting from The Lunduke Journal has been found and verified!

Part of responsible journalism is a relentless dedication to the facts.  This means that, when an error is discovered, it is critically important that the publication not only correct that error... but loudly and publicly announce it.

The Factual Error

In an August 20th, 2023 article -- entitled "The Wiki Piggy Bank" -- I go in depth on the financials of Wikipedia (and the Wikimedia Foundation which runs it).

In one portion of that article, I discus the "Wikimedia Endowment".  A fund worth over $100 Million dollars.

In that portion of the article, I made the following statement regarding the source of the funds for this endowment.

"If Wikimedia Foundation only contributed $30 Million (from user donations) to the Endowment... who contributed the rest of the money?  A company?  Rich benefactor?  (No... it's not listed.)"

That statement... was factually incorrect.

Source: The original revision of "The Wiki Piggy Bank", published August 20, 2023.

It turns out that some of that information is, in fact, made publicly available... The Lunduke Journal simply missed it.  An unfortunate error, as the details of this funding raises significant questions about Wikimedia and, quite honestly, makes the story even more interesting.

Source: Wikimedia Endowment Benefactors

George Soros.  Google.  Facebook.  While there are plenty of other names on the list of "benefactors", those three immediatly jump out as raising significant concerns regarding their potential control of Wikipedia.

Why did Wikimedia not correct this error?

Worth noting: The Lunduke Journal reached out to the Wikimedia Foundation, both before and after publication of the original article, for comments or corrections.  None were ever provided.  That article went on to be seen -- in one form or another -- tens of millions of times (across a number of platforms) over the months that followed.

Wikimedia was aware of the contents of this article.  When The Lunduke Journal published the statement that their benefactors were "not listed"... they would have immediately known that this was an error.  As portions of the article were shared, screenshoted, and quoted millions upon millions of times... they would have been reminded of that error.  Repeatedly.

Which begs the question... why not correct the error?

The answer appears fairly obvious: They did not correct the error... because they did not want the error to be corrected.

Because, we can assume, the truth is worse for them than the error.

George Soros is among the most polarizing -- and most hated -- persons on Earth.

And, considering the pointedly political agendas and spending of the Wikimedia Foundation, the direct funding and involvement of George Soros only adds "fuel to the fire" in terms of concerns being raised.

I wish that I had caught this error prior to publication as it makes the story even more interesting.  But I certainly see why The Wikimedia Foundation was not keen on these facts getting more widespread coverage.

Error Corrected

This error has been corrected in the original article.  I am also publishing this article, standalone, to announce the error.  I will the follow up by publishing both a podcast and a video declaring both the error and the correction.

I want to thank The Lunduke Journal reader who sent in this correction.  It is deeply appreciated.

Read full Article
See More
Available on mobile and TV devices
google store google store app store app store
google store google store app tv store app tv store amazon store amazon store roku store roku store
Powered by Locals