@santi @muito_pelo @goosey propably because they want to renew interest amd potentially gain new licensees.

• Not shure why anyone would choose #RiscOS in 2026 and it's "Cooperative Multitasking" but maybe a 'mature codebase' makes it more interesting. Similar to #OpenVMS ¹, #QNX ², #VxWorks ³ and #WindRiverLinux ⁴ trying to increase adoption by those that demand a more hardened and deterministic performing OS…

@w84death @whitequark @landley the idea behind @OS1337 is not dissimilar from #VxWorks and #WindRiverLinux in that one can build their own #custom minimalist #Linux...

• It's still in early concept but longterm I do intent to flesh it out into something more useful, maximizing the abilities one has with #Frugalcomputing, because an 80x25 #Terminal should be all that's needed still...

https://os1337.com

@mrmasterkeyboard @landley glad I could get you guys connected then...

I'm convinced #toybox is a good #userland to get a basic OS up and running and on it's feet. If it's good enough for #Android then it's certainly gonna be good enough for #embedded stuff as well...

• After all that seems to be the main goal of it: Allowing "self-hosting" as in building itself under itself if not deliver under the same OS...

I don't leverage that capability with #OS1337 (at least for now) but that's because I treat it more akin to how #VxWorks and #WindRiverLinux is being developed and deployed...

@landley @DavittoKun *nodds in agreement*

I don't expect anyone maintaining, designing or building #CriticalInfrastructure to ever reach out to me or even use OS/1337, but if those developing i.e. medical IT take a look at this and decide to use a clean and minimalist #Linux, #FreeBSD, #OpenBSD or even #illumos - based distro with #toybox or another compact #Userland instead of some botched "embedded" Version of Windows, then already that's the kind of change I want to see...

I mean it would be cool if they used and contributed to #OS1337 but if I wanted to force them then I should've made some commercial distro akin to #WindRiverLinux or #VxWorks instead, and I don't...