Educational/hobby OS

The idea occurred to me right now as haiku is fully built off of C++ and usually a lot of wanna learn how to develop games and build code, based off of personal experience haiku is one of the only OSes that actually teaches you how to use code and it can be a nice friendly hobby, haiku is very easy to use is very fast and you can get the hang of code very easily with you eventually learning how to port game or write scripts, so basically what I’m trying to say is why not mark haiku as both a hobby OS and a educational OS, because surprisingly a lot of children specifically teenagers are actually very interested in code and a lot of grown people too, especially since haiku actually excels in teaching code better than Linux does, and oddly enough, you could get haiku to run on a tablet and get a kid a pin for the tablet and they will learn how to code that way since haiku accidentally has touchscreen support

Thank you for taking time to read this :face_savoring_food::face_savoring_food::face_savoring_food:

1 Like

That’s an idea! A hobby and/or educational OS doesn’t have the same kind of pressure on it; expectations are lower, which may be a better match for Haiku’s current state.

Explain?

The API documentation is split between two reference sources. There are resources, but they are not actually part of the OS.

I think based off what I used on haiku, Genio and Qt Creator are the best app are the best for developmental environments and could help a lot and based off of this article I think haiku offer online pdf on C++ as shown here Learning to Program with Haiku | Haiku Project

I agree also, I think the API documentation and the tutorial must be improved before considering it’s «Educational » :slight_smile:

Even for those examples there, something like Kate or any editor with a “Terminal” integration will do.

I mean, yeah, but it was more trying to help the point that we can use haiku as a educational OS plus there’s low expectations and less pressure on the developers if it was a educational OS as it’s meant to teach something and best stuff for most of my forums posts it was always relevant that someone managed to learn C++ and get into developing with haiku than it was ever present for them to with Linux or window plus it can also be a hobby OS I feel like haiku is really one of those apps that can really just expand its ecosystem just because of how simple it is it’s simplicity is what helps it. Do these things and it’s terminal integration helps it even more and it can allow people to port their own games and give haiku a unique set of games and ports, especially for people who wants to play specific games and wants to expand the ecosystem, that in that haiku similarly always seems the boot with android based tablets and has accidental touchscreen support because for some reason when I tested it a while back with a touchscreen computer, the system kept thinking it was a mouse or something else and always allowed it to enable touchscreen so it’s a win-win and we can put a accidental feature to use and help people code

There are users who use Haiku. Including some of the developers. I don’t think telling to them “but it’s just educational” is a great idea.

It is educational, in a way, yes. I’ve been participating in Haiku for more than 15 years now, and I’m still learning new things every day (about how an operating system works, about how open source projects can organize, about community management, and a lot more things).

But it is also so much more than that. It is a real and serious operating system, that people actually use. And by being this way, we also get to learn about long term maintenance, the compromises and tradeoffs to remove broken code while not breaking things that rely on it, how to provide long term maintenance for such a big project, how to manage stable (beta) branches and development branches so that our users have a stable system to use, and so on.

All of this without too much pressure on the developers, I hope. Or at least we’re trying to do that. We achieve it by having a quite decentralized process (so that one single person doesn’t end up responsible for everything, and if a developer has other things to do, for a month or two or even several years, that’s not a problem). We do that by being very careful about not setting fixed dates for milestones, so if things take longer than expected, no one gets into any problems.

Basically, if you are a developer or want to become one, pick a problem to fix, find a way to solve it, and then if you want more, try to find the next, possibly larger problem. Stop whenever you want. Come back whenever you want. You will not be responsible alone for that part of the code, other people can step in if needed. That explains why we have a quite strict code review process, making sure at least two persons understand each part of the code: the one who wrote it, and the one who reviewed it.

8 Likes