Live data from Hacker News

Got an old Raspberry Pi spare? Try RISC OS. It is, something else

theregister.com

1–10 of 205 posts

Re: Got an old Raspberry Pi spare? Try RISC OS. It is, something else

#2
I’ve got fond memories of RISC OS from my school’s room full of Archimedes. I spent a a fair bit of time designing and failing to build a text adventure in Basic, while my teacher tried to get us to learn how to use TechWriter. Best feature was being able to drag a slider to create a RAM disk.

Amazingly you can still buy a copy of TechWriter 9.1 for £85! http://www.mw-software.com/software/ewtw/ewtw.html

Re: Got an old Raspberry Pi spare? Try RISC OS. It is, something else

#3
I kind of went down a rabbit hole last year after the Xerox Star emulator was posted here. It was really cool, but super slow, so I felt like emulating another old system. I ended up writing a GUI calculator for RISC OS in ARM assembly, neither of which I had exposure to before. It was a blast. Very interesting system, it's like visiting a country on the other side of the planet.

There's a pretty good emulator, they've got a bundle fully loaded with all kinds of RISC OS tools.

https://www.marutan.net/rpcemu/easystart.html

Re: Got an old Raspberry Pi spare? Try RISC OS. It is, something else

#6
RISC OS has been limping on thanks to the efforts of some extremely hard-working volunteers, but a roadblock is coming. The Pi 5 drops support for 32-bit ARM code, in which RISC OS written, and since enormous chunks of it are written in assembly, there is no trivial way to port.

Even so, it's heartwarming that people continue to put efforts into operating systems that aren't related to Unix or Windows. I'm happy to see people use this, and AmigaOS, and BeOS, and others. Computing shouldn't be a monoculture.

Re: Got an old Raspberry Pi spare? Try RISC OS. It is, something else

#7
It was ahead of its time in UX, but rather behind in the foundations. It's a single user system with no real security, and there was no system of shared libraries - to share code between applications, it was usual to put the shared code in a kernel module and call the kernel. Even the standard C library worked this way.

Amusingly, when you invoked the system console -which was at a lower level than the gui system, effectively pausing it - the command line appeared at the bottom of the screen and the frozen gui scrolled up as you entered more commands; until you exit the system console. (It was also possible to get a command line in a window, which could do slightly less - I forget exactly what)

Post reply on HN