Submitted by RISC OS 5.24 has been released.
The headline features see previously neglected areas of RISC OS dragged kicking and screaming into the 21st Century, with JPEG support, monitor EDID support, handling of larger hard drives, and the network stack being upgraded. The bounty system is delivering some really worthwhile enhancements into the software. USB and network stack improvements are a massive undertaking, and ROOL broke each into several stages to make them more manageable.
There are also some genuine improvements to user features such as clipboard improvements and new features in Paint. Lots of applications have received little tweaks such as unicode and fancy fonts in Chars, improved dialogs in Printers, tweaks to HForm, DosFS, Maestro, more secure LanmanFS which can connect to Windows 8 and 10, etc.
RISC OS 5.24 is freely available for Raspberry Pi machines.
RiscOS and Haiku/Fuchsia are two serious alternatives to Windows/Linux
While the kernels used in Haiku und now Fuchsia share some concepts and even some authors are the same, both are definitively very different animals.
in my opinion they share the same vision: an operating system more tied to the hardware. Like AmigaOS, RiscOS, Syllable and BeOS haiku and fuchsia kernel give more possibilities to programmers (like me).
You do not have the unlimited access to hardware on BeOS or Haiku, that you used to have on Amiga or old RiscOS.
And for Fuchsia this is totaly wrong: all APIs will be highly abstacted.
As long as you are not developing drivers, nothing of the underlying hardware will be exposed.
Then your opinion is objectively wrong.
Haiku OS isn’t tied to the hardware any more than Windows NT is, the only thing stopping ports are that there are no people wanting/doing ports. The core concepts are as all modern systems mostly portable.
And Fuchsia is also designed for portability.
Possibilities to do what? What kind of projects are you working on where being tied to the hardware is an advantage?
Aside from games, demos, and some examples of controlling external equipment I am not sure what benefit you would have.
I am not discounting those cases, but I am curious why you feel you need it
They both are realtime OSes, best suited for multimedia and gaming applications. I currently use Haiku / BeOS api for realtime data acquisition via environment sensors.
No: BeOS os Haiku are no RTOS.
They may almost behave like one, if your task it the only one running, but this is real-time by chance and not by design.
Have a look at FreeRTOS.
Edited 2018-05-07 08:35 UTC
So by this point you now now that neither BeOS nor Haiku are RTOSs. I would also like to point out not only is RiscOS not real time, it isn’t even preemptive. It uses cooperative multitasking.
On top of that being a RTOS doesn’t have to be close to the hardware, or even fast. It means that task switching is deterministic (amongst some other things).
Finally you may not even need a RTOS for realtime monitoring, as evidenced by your use of Haiku
I really want to underline something: real-time doesn’t mean fast. Some of them are, but it doesn’t mean that. In a hard real time system it means that a context switch — from the task scheduler, a timer, or an external interrupt — happens in a deterministic amount of time. It also implies that there are things like watchdogs that will restart a hung/crashed process, and that and that a runaway process cannot bog down the entire system.
So a system that has a one hour context switch time is still real time.
But also, because that context switch time is a contract it means that I/O operations may be slower than on a OS like Windows; because they have to be interruptible. Therefore they aren’t always ideal for when you need to be close to the metal
Great, I want it… too bad it’s SO HARD to ADD A LINK in that wall of text, FFS.
Here is the link: https://www.riscosopen.org/content/downloads/raspberry-pi