World: r4wp

Maybe they're both wrong.

If you stretch the definition to conform to your argument, then yes, 
you can make anything fit

But syntax incompatibility for the same datatypes is a bug. The only 
question is which language needs to change to make it compatible. 
I am not going to constrain Red to match what R3 can do now when 
R3 can change too. They are related languages. Arbitrary incompatibilities 
that aren't related to the differences in semantic models are bugs. 
Of course this is all keeping in mind that LOAD is just a function, 
but that doesn't make arbitrary incompatibilities a good idea. They 
are in the same syntax family. If it's a good idea to do for Red, 
it's a good idea to do for R3 as well. And if it's not a good idea 
to do for R3, then it is likely also not a good idea to do for Red 
for the same reasons. And maybe there is a better idea for both.

Semantic incompatibility is another issue. Those are more likely 
to be OK.

Hex notation is not arbitrary

So the bug is in R3.

It is likely that there will be whole datatypes that are appropriate 
in one and not the other, but I expect many of those to eventually 
cross-propagate in a lot of cases because their system models aren't 
really that different, just their implementation models. Certainly 
I would expect datatypes with literal non-constriction syntax to 
cross-propagate eventually, and those are the only ones where syntax 
compatibility would be something we would even consider to be an 
important factor.

If you define anything Red does that R3 can't do as a bug, that's 
fine with me :-)

The main principle of the Rebol family way is data syntax compatibility. 
Everything above the data syntax is just a dialect. Even construction 
syntax is a dialect.

Tell that to Boron and World

Incompatibility is the whole point to Boron and World, and that is 
why they will eventually fail. I want to make Red and Rebol succeed. 
They have the best chance to succeed by cooperating. No merger necessary, 
just cooperation.

I don't think that can be said of World

If you define anything Red does that R3 can't do as a bug, that's 
fine with me :-)

 - only when the reason that Red does it is sound. I've noticed that 
 sometimes it isn't (don't worry, it's rare). On those occasions, 
 I'll report Red bugs :)

I think that it can, but the reasons for that are not relevant here. 
If you like I'll discuss them with you privately.

No need, I'd like to get on with my work

Cool.

BrianH: I agree that we should avoid arbitrary syntax incompatibilities. 
For achieving that, the best way is first to have a complete formal 
description of the target syntax that we all agree on, then only 
we'll be able to flag deviations from that model as bugs. 


IIRC Chris has started working on such formal description, how complete 
is it?

Looks like we need to find some simple but efficient online collaboration 
tool to better keep track and organize all the common sub-tasks between 
R3 and Red that keep poping up these days.

I have that bookmarked, but haven't yet looked it over thoroughly. 
I noticed that the last time I tried to determine R3 syntax the effort 
generated a lot of bug tickets. The same would likely happen once 
I get a chance to go over Red syntax, and they may end up being a 
lot of the same bugs. Some syntax issues are an inevitible result 
of being in the same syntactic family, and not realy arbitrary when 
you consider the balance of the entire syntax.

For instance, there is at least one bug report for R3 related to 
increasing the number of delimiters that should be rejected because 
implementing it would drastically reduce the readability of code 
written in any Rebol family language. If Red implemented that proposal 
it would be a bad thing for Red as well for the same reasons.

And I was the one who filed the bug report :(

Boron may fail because people just don't seem to be interested in 
it and World already failed because it's closed soirce.

I don't think World failed, actually. I think it succeeded at what 
he needed it to succeed at. He just didn't need adoption by other 
people.

As Geomol doesn't list World in used tools for his iOS projects I 
guess it failed.

Sounds like Brian means Boron

Doc, the Brackets editor is using Trello for the online task tracking/collaboration. 
Looks pretty cool and doesn't cost.
https://trello.com/board/brackets/4f90a6d98f77505d7940ce88

World's value slot size is 256 bits, which only makes sense for big 
data, not for mobile platforms like iOS. Its semantic model is basically 
that of R3 (plus all of the changes that he had requested R3 make 
that were rejected), and that semantic model is not really compatible 
with the iOS App Store review process. So I'm not surprised to see 
him not use World for iOS - its target market is completely different.

Kaj, are you sure? "He just didn't need adoption by other people." 
sounds like closed source nature of World, not Boron's GPL.

He released documentation, not the actual interpreter. He needed 
advice, not adoption.

Boron is meant to be used by a lot of people, hence the copyleft 
license and actually being released.

I often have no idea what's in Brian's head :-)

I must confess that I have one very big and irrational problem with 
Boron. It has same name as one extremly stupid Czech heavy metal 
band. I just cannot work with it, even if it may be great language.

(I will file a bug report for Brian's head ;-)

I met them on one festival where we were playing together and from 
that day I just can't stand Boron.

John needs World to become popular, because his business model is 
to sell a book about it. Karl specifically didn't mean Thune to become 
popular, probably not even ORCA. Boron was meant for a wide audience 
again, but he does not depend on it, because he's simply developing 
it for his work

I was fine with Orca.

That's cool, Rebolek :-)

Having only been exposed (mentally, not physically) to the element 
Boron, I have no prejudice against it's name. And I have a coffee 
cup with an orca on it :)

I know it's pretty stupid but I can't help myself :) That's why I 
was very glad for Red(/System). That and BSD vs. GPL.

ONE MORE TIME: IT'S NOT GPL!

Ah, I didn't know about the book. He only mentioned wanting to use 
it for his projects, which I could only guess at because of its semantic 
model. I mostly knew about it because the World features he was promoting 
the most, beyond the 256-bit value slots, I recognized as being rejected 
R3 tickets.

That's why I said that incompatibility with R3 was part of the point 
to World. He went out of his way to talk about the deliberately incompatible 
features. The only thing left to distinguish it semantically from 
being something in the same category as R2, R3 and Boron was the 
256-bit value slots. Otherwise it was pretty much the same language 
model.

Red is a different language model, of course.

OK, I understand your point

The iOS theory is reversed, though. World is aimed at science, and 
then the iOS apps came just to make money for World development

That makes sense.

Kaj: LGPL? Sorry, I'm not expert at licensing.

Yes, very different

Unfortunately, we are forced to be experts at licensing

Boron is basically like R2, but with a Lua/R3-like library model 
with a different FFI from either, at least in terms of its major 
semantic model. Syntactically Boron has gone out of its way to adopt 
more C-like features here and there. The LGPL argument is more a 
personal and social thing as far as I am concerned, it's not the 
reason for the language design choices. You can tell the reason for 
the language design choices just be seeing which choices were made 
(assuming a reasonably intelligent person).