This is great, thanks for releasing your work. Very impressive.
You may get some interest from others in the retrocomputing/permacomputing sphere if you implement an Uxn emulator; it is extremely simple and can run on very limited hardware. https://100r.co/site/uxn.html
Vintage hardware would be a great host for Uxn programs, so I suspect this would generate some excitement.
Nice! The project also has a 16-bit variant https://github.com/luke8086/gentleos, not clear if it works on 8086 IBM PC, but I'll give it a go. Been looking for a reason to power up my IBM PC again.
Ok, I built the floppy image now. dd'ed it on a floppy and powered my IBM PS/1 up. Despite some nasty sounds of the HDD bearings that went away after 30 seconds, the floppy does not boot on this machine. Just a black screen. 386SX-25 2MB RAM. Maybe 2MB RAM too less, but I thought at least something will happen. :-)
For PS/1 you'll need the 16-bit version from https://github.com/luke8086/gentleos. A floppy image is provided in releases. Note you only need to copy the first 64KB, the rest is just padding for emulators.
Good catch, the yellow and blue colors are totally inspired by BeOS :D I'm even adjusting the default VGA palette to get the right tints in 16-color mode.
I think it's that yellow bar what it makes it look like BeOS. And maybe the right hand menu bar. But once you check a B/W version, it doesn't look like BeOS that much.
> A hobby operating system for vintage 32-bit PCs.
I am all in favour of great projects, but why a differentiation between 32-bits or 64-bits? I don't understand that. Is a computer that is 32 bit or 64 bit, either way which, not worthy?
Edit: I understand a motivation if it is on simplicity choosing one or the other, but other than that I don't see why that should ever be a goal worthy to be pursued. Software should really "just work" no matter the number of bits and bytes.
> Edit: I understand a motivation if it is on simplicity choosing one or the other, but other than that I don't see why that should ever be a goal worthy to be pursued. Software should really "just work" no matter the number of bits and bytes.
In this context, 32-bit means the minimal requirement. You can absolutely run even the 16-bit version on a 64-bit PC, provided it has BIOS/legacy-boot mode.
It only won't work on modern pure-UEFI systems because that would require writing full stack of USB drivers for keyboard and mouse, and that would be a huge task.
x86 boots in 16-bit real mode. Then you need to specifically transition into 32-Bit, and from 32-Bit it can be transitioned to 64-Bit Architecture...
The last step (32-bit to 64-bit) can a bit of a can of worms especially on older platforms where 64-bit implementations can differ greatly and 32-bit "just works tm". 32-bit is quite well supported and has enough resources to make some interesting programs work without much hassle.
I think the author has made the decision not to support 64-bit mode due to needing to balance the complexity and usability of the project. It is a hobby project after all.
Since the author maintains a 16-bit and 32-bit for this project I suppose if you wanted you can always fork and maintain a 64-bit version if you wanted to.
I have a theory that corporations make new UIs to entertain people through them. First, to create the feeling that something is happening, and second, to increase screen time.
Old interfaces were far more practical for getting work done, and therefore obviously boring.
For me, as someone who is supposed to use technology as a tool and not as a source of amusement, the new interfaces of the major OSes feel unacceptable. But the other billion people chatting and scrolling are the real consumers, not me — and as a result, we now have the interfaces we have.
The link is to a designer talking about how technology has led us to a design world that is mostly driven by nostalgia. I personally don’t see it as being applicable here as it deals with big design houses not hobbies, but I can see why someone might think it is.
This is great, thanks for releasing your work. Very impressive.
You may get some interest from others in the retrocomputing/permacomputing sphere if you implement an Uxn emulator; it is extremely simple and can run on very limited hardware. https://100r.co/site/uxn.html
Vintage hardware would be a great host for Uxn programs, so I suspect this would generate some excitement.
Perfect. Nice to see a platform target stability instead of constantly reinventing itself and its APIs. Definitely want to give it a go!
I am all in favour of great projects, but why a differentiation between 32-bits or 64-bits? I don't understand that. Is a computer that is 32 bit or 64 bit, either way which, not worthy?
Edit: I understand a motivation if it is on simplicity choosing one or the other, but other than that I don't see why that should ever be a goal worthy to be pursued. Software should really "just work" no matter the number of bits and bytes.
> Edit: I understand a motivation if it is on simplicity choosing one or the other, but other than that I don't see why that should ever be a goal worthy to be pursued. Software should really "just work" no matter the number of bits and bytes.
Not really how software works.
Just sold my SGI Indigo 2 for 900 $ ! Vintage 64 bit is absolutely a thing. :-)
Personally I’d have said it isn’t. But these terms are subjective.
It only won't work on modern pure-UEFI systems because that would require writing full stack of USB drivers for keyboard and mouse, and that would be a huge task.
The last step (32-bit to 64-bit) can a bit of a can of worms especially on older platforms where 64-bit implementations can differ greatly and 32-bit "just works tm". 32-bit is quite well supported and has enough resources to make some interesting programs work without much hassle.
I think the author has made the decision not to support 64-bit mode due to needing to balance the complexity and usability of the project. It is a hobby project after all.
Since the author maintains a 16-bit and 32-bit for this project I suppose if you wanted you can always fork and maintain a 64-bit version if you wanted to.
Computer programs are tools. It doesnt do anyone any good if they're unusable in the name of chasing moronic trends.
Old interfaces were far more practical for getting work done, and therefore obviously boring.
For me, as someone who is supposed to use technology as a tool and not as a source of amusement, the new interfaces of the major OSes feel unacceptable. But the other billion people chatting and scrolling are the real consumers, not me — and as a result, we now have the interfaces we have.
https://gramsnap.com/en/instagram-reels-viewer/