What does your OS look like? (Screen Shots..)

[frednora]

7th time wow, I can relate to you. Looks like some people just love rewriting their OSes over and over.
What is wrong with C++? What problems did you run into? I've recently (~5 months ago) switched to C++ and things are definitely easier to work with and organize.
Nah, don't go micro yet, that is a really big big switch IMHO, lots of specific things to consider.

It wasn't so much that I had a problem with C++: I love the language, and it can be extremely expressive. If you excuse the ridiculous naming conventions of its standard library, it's incredibly powerful too.

The problem I found was that I got bogged down in details. I'd write my own implementation of std::vector. It would work, but then I'd realise a month down the line that there was a bug in it. I'd go back to fix that, and this became a common thing. The more I tried to create abstractions: automatic reference counting, smart data structures, etc. the more time I consumed working on things that weren't core features of the OS. I got myself stuck in a pit where, for about 2 months, I added virtually no new features to my OS, instead spending my time improving and adding needless overhead to my kernel in an effort to produce correct code.

I moved to C, and things are much nicer. Most code is actually shorter, it doesn't do strange things in the background, you mostly don't have to care about constructing static objects, it doesn't mangle function names (putting 'extern "C"' at the beginning of stuff gets boring very quickly), and the syntax is SO simple that it feels more like you're working with the underlying machine rather than the language. Its syntax seems to be designed to just get out of the way, without any distractions like OO, templating, constexpr, lambda functions, global construction, etc.

My conclusion is this: C++ is superb for userland applications. But for my kernel, I'm going to use C for sure.

I think the same thing.
I'm gonna use C and Assembly for kernel stuff, port some small C compiler for user land ... and that is it.
C++ is a nightmare. I simply can't handle that language at this moment.
Maybe in the future.

[mariuszp]

Revamp of my GUI. Some optimisations, and some improvements in graphics. A bunch of new games and applications

[MajickTek]

Revamp of my GUI. Some optimisations, and some improvements in graphics. A bunch of new games and applications

I love it! Looks professional.

[Sik]

A simple window.

You probably should start using different colors for the text depending on where it's used (I can barely see the text on the titlebar buttons)

[ilmmatias]

Finally, my operating system have keyboard support, and a basic shell!

[Seahorse]

CHOSTeam, your CLI design is lovely.

Gungomanji isn't very bad himself, either.

[ilmmatias]

It's based in bash, but i used colors from text mode.

[MollenOS]

After months of development i finally got my kernel converted to a hybrid micro-kernel. The system layer (in this case i386) and kernel layer (shared code between architectures) are also seperated. All drivers run as seperate user-land processes, and all communication is performed via IPC. This is my usb-stack enumerating an port that the uhci driver told it about.

[ilmmatias]

Now, CHIcago have a basic in-memory file system with working permissions! (Still need to commit this to the repository...)

[Ascended]

Not much to look at here yet. Just started a few hours ago. Still dusting off the cobwebs and finding my feet again.



Basic bootloader running in CGA mode.

[zaval]

^ OS Test. very original name for the OS. jk.
I guess it's not bad for a few of hours.
And this is my humble achievements in like a few of months. :^/
But hey, I now can read multiple blocks from an SD card! Don't believe the screenshot where it's saying it's a single block read, it's CMD18 - Multiple block read, just didn't change the string. We just have read 8 consecutive sectors.
With this speed of progress, I guess HDMI/LCD stuff will get working after a couple of years. Definiteley, we need to accelerate things.

[Ascended]

@zaval Nice!

it has been years since I played with this kind of thing. I stumbled across this site yesterday and the community and wiki info looks awesome. So, I thought I'd give it a crack again.

[frednora]

This window shows me some kernel info.

[FelixBoop]

Finally got interrupts working after about an hour of head-banging and double faults. It's amazing how deep something looks when really you just wrote "0x0c" instead of "0x0d".

Anyway, now I can remap the PIC and import old keyboard driver code.

[bellezzasolo]

Just started the latest revamp.
Currently, I only have the most basic VGA driver. It's not worth working on.
I've gone down the Multiboot2 line, and have successful builds for x86 and x64. I have ARM/ARM64 targets, but I need to work out how to load on those architectures...
I now have a module loader, meaning the kernel doesn't need a particularly advanced paging driver, the HAL is responsible for that. In fact, my kernel paging code is all in assembly.
The kernel itself is written in C++. Mainly, I've been focused on parsing the multiboot2 stuff.