World: r4wp

Is that still on your to-do list Pekr :D

I am in a hurry, I want to report them before release

 drive faster so you will be home before you are out of gas.  "But 
 yes, it's the domain I always wanted to target with REBOL" the domain 
 you want to target is the world isn't it?


I am studying the Red and Red/system sources these days to get more 
of a feeling what is going on.

It looks like there are only function and context definitions. WHere 
does the code start?

Start

 might not be the appropriate term in this context, as the code is 
 modular. What you're probably after are the compilers wrappers:

- for Red: %Red/red.r
- for Red/System: %Red/red-system/rsc.r

Not exactly, I read rsc.r as if system-dialect is not set then start 
with the compiler.r script. (after that or else the rest of the script 
follows) but then is has some do other scripts and a modular part 
and the other scripts are modular too. It look all very sound bu 
somewhere <there must be/I expect> a first action or function call.

rsc: context

 does contain "fail-try "Driver" [main]" that looks like a starting 
 point but it is within the context. So in my mind that does not get 
 triggered.

With Red we can target the world, before that with REBOL we had to 
be more limited. And also, one targets domains that others haven't 
satisfactorily addressed yet. New land is easier to inhabit than 
occupied land

Got the OpenStreetMap GPS Map browser to work on the Raspberry

Good! :)

It's all very slow, though. I don't understand why everyone is so 
excited about the Raspberry if they're all running LInux

I've found a bug in Red on ARM: the polymorphic dispatching isn't 
working.

Don't think I've hit that yet

RPi slowness: I've noticed it too...Even overclocked, at 900MHz, 
the UI still feel sluggish...Amiga 500 was having a fast UI running 
at 7MHz, so no excuse for those bloated UI stacks...

Yes, it's really, really frustrating now that Syllable doesn't run 
on ARM

I really can't understand how the UI stacks nowadays can dare produce 
slow results, with CPU and GPU thousand times more performant than 
the poor A500.

That's exactly why :-)

There's something deeply wrong in the way most so-called "modern" 
OS/desktops are designed. My 133MHz Bebox with a poor PCI video card 
was able to provide a very responsive UI, even under heavy load.


The RPi feels like dying as soon as you launch the lightweight (no 
kidding!) web browser Midori...Of course, the browsing is very slow...I'm 
quite disappointed by that and it's not the hardware fault, the RPi 
is a great platform, but the software stack sucks a lot.

Yes, I can't wait to wipe them all out

What we'll probably get first on Raspberry is RISC OS. I was using 
that in 1987, so looking forward to use it again with Red

At least in the official Raspbian you already have NetSurf, a completely 
custom browser ported from RISC OS

Inlined printing fix confirmed working on ARM with Fibonacci and 
SQLite

I would be interested to know, how would QNX perform on RPi - QNX 
is pure C, no C--, highly modular, async, etc.

Linux is pure C, too

Well, but Linux suxx anyway, so :-)

Well, it's also highly modular, async, etc. :-)

The thing is that they made software so complex, that it has become 
extremely hard to point your finger at where exactly it goes wrong. 
We had to build Syllable to get an idea of some of those things, 
and then nobody wants to believe you

Fixed missing function! pointer dereferencing in ARM backend, all 
my Red tests are now running fine on Linux-ARM backend.

Doc, quick license question: Was the BSL chosen because it allows 
you to distribute a binary without requiring that you distribute 
the license, unlike MIT and almost all other open source licenses? 
Would it be a problem if you incorporated Apache licensed code, which 
doesn't distinguish between source or binaries in this? You probably 
wouldn't have to actually include the license with the product, only 
in a web site or help file somewhere...

almost all other open source licenses

 meaning pretty much everything except the WTFPL or public domain.

The problem is that everyone compiling a Red program would have to 
include the licence with it when distributing

Not with it, they just have to provide it somewhere the recipient 
can get it. The NOTICE thing in the Apache license is weird though.

Yes, with it, or in it

No, just "given". And the requirement to provide copyright and license 
notices only applies to source distribution.

That's not what you said on the blog. Can you quote that from the 
Apache licence?

I clarified later. I would have posted the license link except for 
the sman filter. http://www.apache.org/licenses/LICENSE-2.0.html

It doesn't say that the license must be included with the work, it 
just says that "You must give any other recipients of the Work or 
Derivative Works a copy of this License", it doesn't say how.

There are App Store apps that include a reference to the license 
in their store descriptions, without including them in their apps. 
It can be done.

Sure, but if you don't include the licence and don't code into the 
program where to get it, you're not "giving" it at all

If I put a link on my web site then I'm giving it. I don't have to 
include it, just give it. With BSD and MIT licenses you have to include 
it though.

When you distribute your REBOL program now, you just dump the script 
somewhere, on a web site or in an email or in AltME. To match that 
with Red, you don't want to have to give a licence at all

The length ot the text that you have to manage is immaterial. It 
doesn't matter if you have to manage a few lines of notice or a page 
of the full licence; you just don't want to have to think about it 
for every little progam

The Apache licence was written for a complete web server, the GPL 
is used for complete kernels

It's comparable with the runtime code that GCC compiles into a program 
binary

That has a special linking exception, actually.

Exactly, for the runtime code. Like Red has the BSL

Is there something like the BSL that has Apache's patent grants? 
Because (given that I'm in the US) patents are a bigger issue for 
me.

I'll ask on the blog.

Yes, that would be good. I imagine it would be easy to add an exception 
to the Apache licence

There is no such thing as "not having to provide a license". If a 
license is not provided, then the code cannot be (legally) used.

BrianH asked: "Was the BSL chosen because it allows you to distribute 
a binary without requiring that you distribute the license, unlike 
MIT and almost all other open source licenses?"


With the sole 3-clause BSD, users would need to provide a copy of 
the license with each compiled program, because of the runtime code 
included. So to avoid that, we chose to publish the runtime parts 
of Red and Red/System, under the more permissive BSL terms. The binaries 
that include the compilers (currently that would mean encapped version 
of Red and Red/System compilers) are still under BSD.


When Red will be self-hosted, it will include a JIT-compiler that 
will need to be released under also BSL or similar terms.