heyrick1973 -at- yahoo -dot- co -dot uk

RISC OS is "finally" open source

The big news, right now (asides from Britain shooting itself in the head, Trump insulting everybody, and some rich git I've never heard of failing at hiding his name from accusations of sexual misconduct) is that RISC OS is finally going to become open source.

I put the "finally" in quotes and italics because, as far as I am concerned, RISC OS has been open source for years. There were two small restrictions:

  • You could only build RISC OS for ARM targets
  • Commercial use needed an OEM licence (the price depending upon how soon you planned on feeding changes/enhancements back to the RISC OS codebase)
The first restriction is rubbish. Due to how RISC OS is built, and how tied the entire API is to ARM, there is nobody on the planet who is going to "port it to MIPS for the lulz". The simplest way to get RISC OS on any alien platform is to write an emulator. Anything else is a whole bucket of crazy.

The second restriction was seen as a show stopper by the freetards of the world. You mean, I need to PAY for this?
Actually, no, probably not. I haven't paid a single penny. Because I'm not selling RISC OS or anything with RISC OS inside. This restriction only affected people making commercial use of RISC OS, not random developers wanting to play with it. So that it was a screeching roadblock and a giant barrier to entry is rather untrue.

RISC OS' Castle licence is - this weekend - going to be replaced with the Apache 2.0 licence. For those who don't fancy making sense of the legalese of the licence, it essentially boils down to "do what you want, just don't sue us".

Now, people are saying RISC OS is "finally" open source, because the Apache licence fits in with their personal definition of Open Source (and the OSI definition). Given that I've had the sources on my media for years, and have built my own ROMs with my pet peeves fixed/altered, I gotta say - their definition is more political than logical.

So to big hoo-hah, RISC OS will finally become an OSI accepted definition of "open". It will become a hell of a lot more open than GPL is ever going to be (if it wasn't for the CDDL code within RISC OS, one could legitimately choose to put their copy of RISC OS under GPL; the same is never true of anything licenced as GPL). RISC OS will be freeeeeeeeee!

 

So now the 'tards will be complaining that the official build environment (DDE) is a commercial product. One is forced to pay fifty quid for it. Technically true, but technically false. The DDE does cost, but if a real developer arrived with a responsible and coherent plan for implementing something like a DNS resolver that works in both directions, AirPrint support, or WiFi/Bluetooth/etc, I am quite sure the community will be able to get something happening in that respect. Indeed, one ROOL forum member suggested the possibility of sponsoring a DDE licence to a serious developer.

So, no. I don't agree that the DDE should be free. Because if it was, the big barrier to entry would be our crappy build environment and lack of tools (smile when you use the debugger, because you're getting Punkd, right?).
And if somebody funded porting the best modern IDE available, then the barrier to entry would be the memory protection, or lack of it. Or the co-operative multitasking. Or the how-the-hell-can-you-in-2018-use-cvs (come on, it's better than zip files). Or the fact that it's a massive pile of 32 bit code with no 64 bit support. Blah, blah, blah.

You see, there is always one more excuse to make. One more reason to promise the earth and do nothing.

Instead, let's skip over the lame character building and cut straight to the chase scene...

This is what RISC OS looks like:

Hundreds and hundreds of files. And inside most of them, it looks like this:

Leave your trendy frameworks at the door along with your programming paradigms du jour. The reason RISC OS is ridiculously lightweight (the entire OS runs to a ROM image of around 5MB) and blindingly fast is because the majority of it is written in hand-crafted assembler. The language of the ARM processor. Yes, it is a maintenance nightmare because one can't just recompile to new platforms, but on the other hand it was originally written in 1987 (as Arthur) to run on the new Archimedes range. Back then, writing stuff in assembler was not unheard of, and compiler technology was such that using assembler was often better. RISC OS grew from that humble beginning and... it is what it is today.

There's your massive barrier to entry. Assembler. If you don't know that, you won't get far. You need to be a badass samurai ninja code warrior kitten capable of deftly manipulating stacks and SWIs while talking in the language of the processor. There's no hand holding, and when working at system level (defined as everything that isn't a user mode application), forgetting one single word of data pushed to the stack will freeze the machine. There's no margin for error...

 

To be brutally honest here, I see this announcement as something of a non-event. Okay, RISC OS is now owned by RISC OS Developments so it's a subtle change in direction to make the codebase OSI open source, rather than the previous with-conditions format; however the much bigger news, I feel, is that the rights holder of the 32 bit realm and the rights holder of the 26 bit realm are now talking to each other. Maybe, after far too many years, it's soon to be time to bury the hatchet and leave the past where it belongs. That news is the part that has me excited. But I guess you need to understand RISC OS' history to know what that is important. It's easier to go "oooh" at the announcement that the source code is now available to the world...as if it hasn't been for the past... how many years now?

 

It's the London show on Saturday. There will be more information then. When you attend. In person. The RISC OS world still hasn't quite sussed all that social media stuff yet, has it? ☺ Heck, I bet nobody will even be live-streaming to YouTube. A built-in feature of any worthwhile Android phone made in the last five years or so. <sigh>

 

 

Your comments:

Please note that while I check this page every so often, I am not able to control what users write; therefore I disclaim all liability for unpleasant and/or infringing and/or defamatory material. Undesired content will be removed as soon as it is noticed. By leaving a comment, you agree not to post material that is illegal or in bad taste, and you should be aware that the time and your IP address are both recorded, should it be necessary to find out who you are. Oh, and don't bother trying to inline HTML. I'm not that stupid! ☺
 
You can now follow comment additions with the comment RSS feed. This is distinct from the b.log RSS feed, so you can subscribe to one or both as you wish.

Jeff Doggett, 29th October 2018, 10:38
I was given a DDE licence by a very generous sponsor even though my contribution to RiscOS is pretty minimal. The second time he offered to purchase the update for me I thought long and hard about it and eventually turned it down on the basis that there are more deserving cases. I hope that I didn't offend him too much.

Add a comment (v0.09) [help?] . . . try the comment feed!
Your name
Your email (optional)
Validation Are you real? Please type 28633 backwards.
Your comment
Calendar
«   October 2018   »
MonTueWedThuFriSatSun
134567
891011121314
15161718192021
222324262728
293031    

Advent Calendar 2018
(YouTube playlist)

Japan - can you help?
Japanese Red Cross
日本 赤十字社

Earthquake relief donations have closed.

Read about the JRC
Make a general donation

Last 5 entries

List all b.log entries

Return to the site index

Search

Search Rick's b.log!

PS: Don't try to be clever.
It's a simple substring match.

Etc...

Thank you:
  • Fred
  • Bernard
  • Michael
  • David

Last read at 02:41 on 2018/12/13.

QR code


Valid HTML 4.01 Transitional
Valid CSS
Valid RSS 2.0

 

© 2018 Rick Murray
This web page is licenced for your personal, private, non-commercial use only. No automated processing by advertising systems is permitted.
RIPA notice: No consent is given for interception of page transmission.

 

Have you noticed the watermarks on pictures?
Next entry - 2018/11/04
Return to top of page