Show HN: My self-written hobby OS is finally running on my vintage IBM ThinkPad (github.com)

Appreciate it!

I don't think Haiku runs on raspberry pi either.

Is that 4sec delay something introduce in the pi 4 or 5? At least one guy got the 3 to boot to a Qt app in 2.8 seconds: https://www.furkantokac.com/rpi3-fast-boot-less-than-2-secon...

Supporting variable-width fonts is pretty easy on its own (if bit-packing, you might wish to store them vertically), but does complicate combining characters (remember, they go in different places and may need to make the new character larger).

For vector fonts, the interesting question is "if I render this at a different resolution and then scale it, will it line up?" which fundamentally has no answer that can satisfy everyone. Most other difficulties are merely a Small Matter of Coding (and providing appropriate APIs).

One can really get bogged down in fonts. (-:

http://jdebp.uk./Softwares/nosh/guide/terminal-resources.htm...

If you want a quick improvement over that 8by8 IBM ROM font, I suggest two things:

1. Switch to a 16by16 square.

2. For the ASCII range, go with one of the old home computer fonts, rather than IBM ROMs. Viznut has .hex files for Commodore PET and BBC Micro graphics modes squirrelled away inside Unscii.

I've done the work of upscaling the 8by8 PET font to 16by16, and it works quite nicely as a monospace square font. These old home computer fonts were of course designed to. Whereas in the world of VGA you're soon in trouble with glyphs designed for 9by16.

I had the same problem, I made a 3x4 font that was just barely servicable for the initial project to show text on screen. It was my first (and only) font I ever made! Eventually I needed lower-case, so I turned those into lower-case and made a 3x5 variant for uppercase. It's still not ideal, and I'm sure when I announce my project, people will complain about it. So I've prepared to say "it's a stop-gap solution to make the OS servicable, but we can make more fonts."

I think people skimming a project often just don't quite get how much we pour into our projects, and how very much it cost us. But it's okay, they don't have to understand just how cool it is what we made. At least we know.

When I saw your video of your project, I was thinking to myself, "wow, that's incredibly cool, and I can relate to the steps he's doing!" Just trying to be the voice here of someone who thought that way, in case there are no others.

The power of the crowd compells you.

The power of the crowd compells you.

The power of the crowd compells you.

So what? Someone is not allowed to give constructive criticism?

The fact that the OP built an entire hobby OS complete enough to have windowing and font rendering, and got it booting off his vintage notebook, is extremely impressive, and much more so than the ChatGPT frontends and Chrome reskins that HN usually enthusiastically updoots.

I meant it as sincere constructive criticism! :) <3

I did that all my life: no unicorns but if you do enough things, some will sell auto (once any traction happens I sell: I don't like running a company, I like building stuff). Without all this stress and grifting. Granted, I was lucky that my hobby in 2000 turned out to be worth millions, but it still works fine 25 years later.

I'm not sure it's a bad thing to not necessarily have a plan. Intuition is the hidden sister of logic, both children of reason, and we don't always see her because she's often behind the scenes doing all the work.

Technical debt is as sure as death and taxes. Good software grows over time, like a person growing up. Sometimes you have parts that are needed for a time but not permanently, like baby teeth. That's what technical debt is like.

Other times there are parts that are absolutely ideal long term, but it's a long time before they even make sense. And sometimes things only develop much later than we expect, like wisdom teeth. These are software features that won't make sense until you write the thing that you don't realize yet is only temporary.

I have the same goal of writing everything myself from scratch. It's a very important goal to me for a reason I don't fully understand yet.

Congrats on writing an entire OS, and getting it booting on real hardware! That must be such a rewarding feeling in its own right, even if no one understood how. And it looks so very cool.

You've given me more motivation to announce my project soon. Maybe next week. Thanks.

Have you played around with Zig yet? I hear that would be a good replacement for C here. Did you have any thoughts on porting your OS to that, or did you have any branches some Zig code made its way into?

I'd like to second the mention of plan vs. no plan.

Having no plan is often better when you're facing a deep pit of work, pick at it every now and again, whatever you feel like working on that day.

vs. having a clear Todo list that is longer than a DNA chain and just giving on it after item 5 because 6 is boring.

Oh, and congrats, looks great.

Linus' original plan was to write Linux to learn every feature of the i386. Compatibility with other systems came later.

See the message from Linus Benedict Torvalds on 26/08/1991

https://groups.google.com/g/comp.os.minix/c/dlNtH7RRrGA/m/Sw...

Regarding a plan, I often feel the same way about my own project. There are a number of systems I've rewritten multiple times, and I can't help but think much of that would have been unnecessary if I had been more tedious about diagramming out my needs and requirements beforehand. Other times I wonder if I would have gotten this far had I planned things out... It's the age old question of "would I have started this project if I had known how much time and effort it would have taken?"

Each approach has a clear set of pros and cons, as others have explored in this thread. In the end, I think what ultimately matters is whether we're satisfied (and proud) of a project after a significant amount of progress has been made.

I also took the "I want to write everything myself" approach with my project since I wanted it to be a demonstration of my abilities. I wanted to prove to myself and others I could create a project of significant size and scope. It seems like this often means working without libraries and having to reinvent the wheel over and over again. It's tedious, but it certainly adds to the satisfaction you get as you look over your work and think "this is truly mine; I did this."

And yes, copy ideas, not code, is one of those things I do my best to adhere to. Sometimes, at least with JS, you run into problems, look into solutions, and it turns out there's really only one sensible way to do something; what you end up writing feels like a boilerplate solution to the problem. I often find myself going back and forth through search results from places like Stack Overflow and trying to siphon out the best techniques and ideas from multiple examples to mesh together into some usable code in a style I prefer.

Finally, since I failed to say this eariler, congrats on your project! I'm gonna have to try it out as soon as I get some extra time.

Great, good luck :) It was a reference to the original Linux announcement in 1991,

> I'm doing a (free) operating system (just a hobby, won't be big and professional like gnu)