frontpage.
newsnewestaskshowjobs

Made with ♥ by @iamnishanth

Open Source @Github

fp.

Start all of your commands with a comma

https://rhodesmill.org/brandon/2009/commands-with-comma/
187•theblazehen•2d ago•54 comments

OpenCiv3: Open-source, cross-platform reimagining of Civilization III

https://openciv3.org/
678•klaussilveira•14h ago•202 comments

The Waymo World Model

https://waymo.com/blog/2026/02/the-waymo-world-model-a-new-frontier-for-autonomous-driving-simula...
952•xnx•20h ago•552 comments

Jeffrey Snover: "Welcome to the Room"

https://www.jsnover.com/blog/2026/02/01/welcome-to-the-room/
25•kaonwarb•3d ago•20 comments

How we made geo joins 400× faster with H3 indexes

https://floedb.ai/blog/how-we-made-geo-joins-400-faster-with-h3-indexes
124•matheusalmeida•2d ago•33 comments

Unseen Footage of Atari Battlezone Arcade Cabinet Production

https://arcadeblogger.com/2026/02/02/unseen-footage-of-atari-battlezone-cabinet-production/
61•videotopia•4d ago•2 comments

Show HN: Look Ma, No Linux: Shell, App Installer, Vi, Cc on ESP32-S3 / BreezyBox

https://github.com/valdanylchuk/breezydemo
233•isitcontent•15h ago•25 comments

Monty: A minimal, secure Python interpreter written in Rust for use by AI

https://github.com/pydantic/monty
226•dmpetrov•15h ago•121 comments

Show HN: I spent 4 years building a UI design tool with only the features I use

https://vecti.com
332•vecti•17h ago•145 comments

Hackers (1995) Animated Experience

https://hackers-1995.vercel.app/
498•todsacerdoti•22h ago•243 comments

Sheldon Brown's Bicycle Technical Info

https://www.sheldonbrown.com/
383•ostacke•20h ago•96 comments

Vocal Guide – belt sing without killing yourself

https://jesperordrup.github.io/vocal-guide/
37•jesperordrup•5h ago•17 comments

Microsoft open-sources LiteBox, a security-focused library OS

https://github.com/microsoft/litebox
360•aktau•21h ago•183 comments

Where did all the starships go?

https://www.datawrapper.de/blog/science-fiction-decline
20•speckx•3d ago•9 comments

Show HN: If you lose your memory, how to regain access to your computer?

https://eljojo.github.io/rememory/
291•eljojo•17h ago•181 comments

An Update on Heroku

https://www.heroku.com/blog/an-update-on-heroku/
413•lstoll•21h ago•279 comments

ga68, the GNU Algol 68 Compiler – FOSDEM 2026 [video]

https://fosdem.org/2026/schedule/event/PEXRTN-ga68-intro/
5•matt_d•3d ago•1 comments

Was Benoit Mandelbrot a hedgehog or a fox?

https://arxiv.org/abs/2602.01122
20•bikenaga•3d ago•10 comments

PC Floppy Copy Protection: Vault Prolok

https://martypc.blogspot.com/2024/09/pc-floppy-copy-protection-vault-prolok.html
66•kmm•5d ago•9 comments

Dark Alley Mathematics

https://blog.szczepan.org/blog/three-points/
93•quibono•4d ago•22 comments

How to effectively write quality code with AI

https://heidenstedt.org/posts/2026/how-to-effectively-write-quality-code-with-ai/
258•i5heu•17h ago•200 comments

Delimited Continuations vs. Lwt for Threads

https://mirageos.org/blog/delimcc-vs-lwt
33•romes•4d ago•3 comments

Female Asian Elephant Calf Born at the Smithsonian National Zoo

https://www.si.edu/newsdesk/releases/female-asian-elephant-calf-born-smithsonians-national-zoo-an...
37•gmays•10h ago•12 comments

I now assume that all ads on Apple news are scams

https://kirkville.com/i-now-assume-that-all-ads-on-apple-news-are-scams/
1073•cdrnsf•1d ago•454 comments

Introducing the Developer Knowledge API and MCP Server

https://developers.googleblog.com/introducing-the-developer-knowledge-api-and-mcp-server/
60•gfortaine•12h ago•26 comments

Understanding Neural Network, Visually

https://visualrambling.space/neural-network/
291•surprisetalk•3d ago•43 comments

I spent 5 years in DevOps – Solutions engineering gave me what I was missing

https://infisical.com/blog/devops-to-solutions-engineering
150•vmatsiiako•19h ago•71 comments

Why I Joined OpenAI

https://www.brendangregg.com/blog/2026-02-07/why-i-joined-openai.html
154•SerCe•10h ago•144 comments

Show HN: R3forth, a ColorForth-inspired language with a tiny VM

https://github.com/phreda4/r3
73•phreda4•14h ago•14 comments

Learning from context is harder than we thought

https://hy.tencent.com/research/100025?langVersion=en
186•limoce•3d ago•102 comments
Open in hackernews

8x19 Text Mode Font Origins

https://www.os2museum.com/wp/8x19-text-mode-font-origins/
73•userbinator•5mo ago

Comments

michalpleban•5mo ago
Something I was wondering while reading the article: why? Why would you create a 8x19 font if you already have a 8x16 don't? The answer is: so that you can use a standard 640x480 VGA resolution instead of of 640x400 to display 25 lines of text.
fredoralive•5mo ago
Of course that asks the question of why use the graphics mode for text, which I would suspect was simply to show the seemingly obligatory Energy Star logo, but these Intel boards don’t have it.
bananaboy•5mo ago
This apparently was a text mode not a graphics mode. It would have been a tweaked text mode since the standard mode 3 text mode that you can set via int 10h is 720x400.

The energy star logo was also displayed in text modes - by using custom font glyphs!

michalpleban•5mo ago
It's not a graphics mode. It is just a resolution from the graphics mode, repurposed for the text mode. The reason possibly being the 640x480 resolution is universally supported while 720x400 is not - for example my HDMI TV can still display 640x480.
bananaboy•5mo ago
CRTs were still commonplace though based on the bios dates in the blog. So 720x400 would still have been well supported. It’s strange that they did this!
the-rc•5mo ago
Unlike CRT screens, LCD ones from that time had usually a fixed resolution and wouldn't resize the image on the fly.
martijnvds•5mo ago
The Energy Star logo tended to be made up of custom characters in text mode.

https://www.youtube.com/watch?v=uAHGKanqO6s

pwdisswordfishz•5mo ago
Later versions used true bitmaps, though.

http://fileformats.archiveteam.org/wiki/Award_BIOS_logo

jefftk•5mo ago
I'm still confused: why not stick with 8x16 and go from 25 to 30 lines of text? Is it that you need to support both 640x480 and 640x400?
spogbiper•5mo ago
There was a long legacy of using 80x25 and lots of software that would assume this layout. I think that comes from an even older legacy of dumb terminals such as the VT100 that used 80x24 plus one line for a status line. BTW 80 columns comes from an even older legacy of IBM punch cards having 80 columns. Basically, anything that wasn't 80x25 was going to break a lot of things
f1shy•5mo ago
And the 80 columns come (losely) from a still older standard in typography, of about 70 characters per line, found empirically as a good size for a line. Even today is good design practice in UI, Web and books to stick to 60 to 80 CPL.
aardvark179•5mo ago
The reason for it in terminals is much more directly linked to the IBM punched card format.
michalpleban•5mo ago
Because 80x25 uses 4kB of RAM (one byte for character + another byte for attributes) whereas 80x30 would grow beyond 4kB so you would need 8kB. Maybe not a big deal in a VGA card, but everything was standardized on 80x25 from the olden days of MDA/CGA which had little video memory, so a lot of software expected that.

Plus, making the characters shorter would make them also a bit less legible.

f1shy•5mo ago
And maybe cost also? Not sure, but back in the days maybe 4kB more would have a noticeable (albeit I do not think extrem) effect on final price.
michalpleban•5mo ago
Not in the days when these BIOSes were written, but in the early eighties, yes; the original IBM MDA card had only 4kB memory (enough for just one screen of text) because memory was expensive. So sticking to 80x25 was kind of important back then.
JdeBP•5mo ago
For the execution environment in which firmware SETUP ran, there were often hardwired assumptions, particularly in the parts of SETUP that provide full-screen TUIs with menus and entryfields and pop-up help boxes and whatnot, that the screen was 25 rows high.

Also remember that SETUP as a whole was often a mess of different ROM programs from different manufacturers. Far too many thought it their own ROM's business to clear the display and set text mode before they splashed their copyright strings, prompts, self-test, and hardware auto-detection information up.

Yes, they could have done things properly. The way to detect an existing screen size was there from the VGA onwards. And they could have left the display uncleared. And the whole preserve-my-graphical-splash-screen thing eventually did happen.

They did not.

userbinator•5mo ago
The way to detect an existing screen size was there from the VGA onwards.

When you only have a few KB in total for your option ROM, that's a luxury you can't afford. You can either sacrifice some other important feature of your product to appease the tiny minority, or assume 80x25.

0points•5mo ago
Because standard.

There was also small .com utils circulating that would change to a tiny font so you could have 40, 50 rows of text with tiny fonts, or maybe even more.

bluedino•5mo ago
One of my favorites let you do 132x43, too tiny on my cheap 14" though

Text editors like EDIT.COM and the Borland IDE let you select 80x43/50 in the menu

p1necone•5mo ago
> Is it that you need to support both 640x480 and 640x400

Probably.

A lot of software back then was rendering UIs with box drawing characters, doing complicated layout etc - it's probably much easier to retrofit existing software to output the exact same thing in a slightly higher resolution font than to make the display logic support different resolutions properly.

ape4•5mo ago
I am oddly happy that there's an OS/2 museum
masfuerte•5mo ago
This article [1] has a little more information about the font. Supposedly it first appeared in "Intel's Hi-Flex BIOS".

The source for the font appears here [2] with an Intel copyright.

[1]: https://wiki.softhistory.org/wiki/PhoenixBIOS_4.0_Release_6....

[2]: https://github.com/tianocore/edk2-codereview/blob/0a5f23c06d...

ronsor•5mo ago
Important reminder that bitmap fonts are not copyrightable in the United States of America.
masfuerte•5mo ago
It's more complicated in the UK but font-related copyrights "only" last for 25 years, so 1990s fonts are well clear now.
Aardwolf•5mo ago
There are many aspect ratios of fixed width fonts (see https://int10h.org/oldschool-pc-fonts/fontlist/), from square to rectangular, and this one is more than twice as tall as wide

Is there any info or research on which width/height ratio of a fixed width font is the best for readability?

duskwuff•5mo ago
Don't forget that a lot of old PC graphics modes weren't 1:1. 640x200 was a thing, for example - the pixel ratio is 3.2:1, but it gets vertically stretched to a standard 4:3. An 8x8 font wouldn't look square in that graphics mode.
phalanx104•5mo ago
0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 1,1,1,1,1,0,0,0, 0,0,0,0,0,0,0,0, 0,1,1,0,1,1,0,0, 0,0,0,0,0,0,0,0, 0,1,1,0,0,1,1,0, 1,1,0,0,0,1,1,0, 0,1,1,0,0,1,1,0, 0,1,1,0,1,1,0,0, 0,1,1,0,0,1,1,0, 0,0,1,1,1,0,0,0, 0,1,1,0,0,1,1,0, 0,0,1,1,1,0,0,0, 0,1,1,0,0,1,1,0, 0,1,1,0,1,1,0,0, 0,1,1,0,0,1,1,0, 0,1,1,0,1,1,0,0, 0,1,1,0,0,1,1,0, 1,1,0,0,0,1,1,0, 0,1,1,0,0,1,1,0, 1,1,0,0,0,1,1,0, 0,1,1,0,1,1,1,0, 0,0,0,0,0,0,0,0, 1,1,1,1,1,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0, 0,0,0,0,0,0,0,0,
wpollock•5mo ago
HN is family friendly. Please don't use such language!
EvanAnderson•5mo ago
Aside: Going down the "memory lane" of Intel motherboard codenames was fun. Tuscon II, Anchorage, Atlanta, Seattle, Maui, etc.

I really enjoyed Intel's desktop boards. They weren't particularly flashy, and there were certainly "duds" in there (early MU440EX revs not handling Pentium II CPUs properly, the whole RAMBUS debacle) but in general Intel made a solid (and not at all flashy) board.

With Intel's manufacturing competency you could be assured every board would be consistent. If there was a defect (I'm looking at you, MTH in the 820 chipset) every board would consistently have the same defect.