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.
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.
> 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.
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.
> The only future plans are bugfixes, optimizations, and adding more apps.
Perfect. Nice to see a platform target stability instead of constantly reinventing itself and its APIs. Definitely want to give it a go!
A pre-build floppy disk image would be great, so I could run it on my IBM PS/1 from a floppy.
There seems to be an 8 meg image here: https://github.com/luke8086/gentleos32/releases/download/202...
This is a hdd image, I guess.
Someone prepare a set of floppy disk images so you can get the proper installation experience.
Made me think of Breadbox Ensemble, which is GEOS, and was really lovely.
GUI looks a but BeOS inspired, but somehow even cleaner.
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.
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.
“Vintage” 64 bit PC’s aren’t a thing.
> 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.
The DEC 3000 would like to have a word with you.
> “Vintage” 64 bit PC’s aren’t a thing.
Just sold my SGI Indigo 2 for 900 $ ! Vintage 64 bit is absolutely a thing. :-)
they said PCs
Don't worry, this is portable to both vintage word sizes: 32 and 16.
32 is vintager vintage
32 bit vinteger ;-)
You can do 32 bit voolean too, great for that vintage bitmasks to store application flags. =]
I’m just going to leave this here… https://www.instagram.com/reel/DY_UkH8Ry0V/
That video's bullshit. People prefer old UIs because modern ui is shit, not because they're not creative.
Computer programs are tools. It doesnt do anyone any good if they're unusable in the name of chasing moronic trends.
So, you poop everywhere you go. Interesting.
I don't really understand GP's message. User's comment history seems pretty normal, why would they drop a random IG link here? Wrong article?
To anyone interested in the video, but without an Instagram account, gramsnap sometimes works. (Imginn.com sometimes works for viewing IG profiles.)
https://gramsnap.com/en/instagram-reels-viewer/
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.