“Moonshots” Initiative to Secure the Future of RISC OS

The situation RISC OS dates to the beginning of ARM and still lives but is 32bit only and in assembly. They have been getting sponsorship for small improvements.<p>32bit Arm is going away.<p>They are looking for the resources for a 64bit port.<p>That seems like an entirely reasonable ask. I don&#x27;t know if enough people are interested but it seems entirely reasonable to ask.

Wasn&#x27;t OpenVMS stuck in a similar situation in the late 1980s, where they had tons of VAX MACRO assembly files they had to transpile to Alpha, then Itanium and nowadays x86_64?<p>VAX is a rather different beast than 32-bit ARM and that bandaid would result in a hybrid 32&#x2F;64-bit operating system, but I wonder if a similar solution could be implemented for RISC OS.

Additional context: <a href="https:&#x2F;&#x2F;www.riscosopen.org&#x2F;content&#x2F;documents&#x2F;risc-os-moonshots" rel="nofollow">https:&#x2F;&#x2F;www.riscosopen.org&#x2F;content&#x2F;documents&#x2F;risc-os-moonsho...</a>

For RISC-OS&#x27;s future, it&#x27;d make sense to invest on a RV64GC port.

I wish it could handle larger disks and had a decent browser.

ROOL is seeking: * Funding partners * Experienced embedded software engineers * Community advocates<p>So they have non of those. What’s the point then?

Any new operating system has to answer the question “why? what will this do that Linux can’t?”.<p>If there’s a good answer to that, sure build it, but Linux is incredibly flexible, powerful, honed, compatible and other things.<p>I see the romance in bringing a historic operating system into the future but without good reason there’s little point.