World: r4wp

I'm just wondering (really, just that): is dev capacity (i.e. Cyphre 
GUI. other's on OSX, 64 bit) the limiting factor to accelerate in 
the short term? Or money?

Both, I guess.

We seem to have a somewhat limited dev pool to start with, and most 
of the people capable and willing to work on R3 are also tied up 
elsewhere (to make a living).

Maarten, from my point of view, it's dev capacity.

Yes, but say I'd poor in $1,000,000 today (hypothetically, I'm trying 
to understand what is needed to accelerate), compared to nothing. 
Assuming Android is  the first step (including encap and device access), 
when woud this be done with and without "unlimited money".

A constructive answer to "when would this be done" would require 
realistic planning based on more than a hypothetical offer.

Staying within the hypothetical realm, I think it's very fair to 
say that it would be possible to get it done sooner than without 
"unlimited money".

(That assessment is based on my view that there is quite a bit of 
capacity available which could work full-time on R3.)

Given money, one of the best uses for it would be to give core developers 
stability to commit, and then build the community, which, to me, 
means providing platforms and toolsets that people see as viable 
alternatives to other languages.

Yes, I'm trying to get a handle on "quite a bit capacity available". 
And then attach a pricetag to it to make it happen.

I would want R3 on Android with GUI, GPS, Camera support. And R3 
64 bit Linux server side ("Core").

encappable

 of course. What do we need to make that happen in terms of development 
 time? Then, how much money do we need fo rthat (nt all developers 
 need to be paid full-time, some do it as hobby). Etc.

Do you see my point? For a target, we need to estbalish a time/money 
budget and ratio.

Yes, absolutely. Any good open source projects to use as a model? 
:-\

Because, if I set R3 for development against Scala/Lift/Akka in back 
ends, it's a long way.... Same on mobile: there's Livecode, Corona, 
all of them more mature. So if I treat R3 as an "investment" of sorts, 
the risk/reward ratio needs to be established

Look at the Scala ecosystem (Akka, Lift, Play). Rails. ...

Right, but how did they get funding and support? For Rails, at least, 
they wanted to build the tool for their own use. And they're built 
on top of other infrastructures.

Someone has to say it's worth it to them to pay for some pieces.

Sun paid for Java, IBM paid for Eclipse. They thought they would 
benefit somehow.

And users have to care about what these new tools bring to the table.

Bit of both in my view. Money to support full time development. And 
the knowlegde to know how to is also sparse. A little bit extra on 
info and tutorial like stuff could maybe get some more people started. 
Google's summer of code like the HAIKU project is putting to use 
is beyond reach for the small base of devs for instance.

We are on the other hand lucky to have the enthousiastic giants we 
have now. It is enough to let the projects live on, but not in the 
way blooming as we feel should be the case. 

Yet the progress even in the last weeks is a great accomplishment, 
cannot be said enough..

(that was my answer for Maartens question from 3:23:44 PM

Some heads must be seriously be put together to talk about financing 
the community effort.

One of my views is a way of providing a webhosting service based 
on REBOL/Red and additional open source technology.

If we had a monetary amount needed, would it be possible to write 
up a Kickstarter campaign to fund R3 development?

shure, as long as you have a precise end-result with milestones, 
 time estimates, and realistic goals.

but would it actually end up working?

My gut feeling is that it would be tough. You need good rewards to 
entice people, and our community is small.

We need more momentum. Meaning a small usable base to start serious 
advocating the pro's with and possibilities of generating a little 
money. Attracting young programmers/students willing to contribute, 
one advantage for students is that not everything is carved in stone 
yet. (Only what we want to achieve and the toolset is chosen)

So you could start with a small Kickstarter campaign just to get 
some momentum going, and then maybe follow it up with a larger one 
once momentum is up.

Still tough. Who is going to pledge that doesn't already?

If we can pitch something about it that would appeal to the general 
public (easy-to-develop apps for Android that also run on embedded 
systems and full computers), then maybe we'll get some new interest. 
 Especially for popular Kickstarter search terms like Android, Raspberry 
Pi, Arduino, etc.

General public
 meaning the general geek public.

It's the IF and MAYBE that I'm concerned about. :-\ Again, without 
rewards, who will pledge?

some ideas for real life apps needed? I have some. Non-geeks need 
apps too.

No tools to make these apps atm

;)

@Graham: GitX; found another alternative very promising, even did 
a fetch(!) from the master branch I wanted but could find nowhere: 
sourcetree 
http://www.sourcetreeapp.com/

Maarten, some thoughts about all this. IMO R3 or what it's than called 
is not the end product. It's an enabeling technology to make good 
products in a very short time.

So, what's interesting about it is, that one gets access to a complete 
vertical technology stack. The black-box dependencies (those that 
you can't influence) are mostly zero. Of course you don't have a 
big community, eco-system etc. around. But I'm coming more and more 
to the point that I don't need a big eco-system, I need the right 
eco-system. I don't want to use big frameworks, zillions of libs 
etc. This all makes product development a hell.

A mean and lean technology stack, that is maintainable, can be adjusted 
to some special needs with the fundamental things available is everything 
you need.

What I would do if I could afford is, is to re-implement R3 using 
the D language. This should result in a more simple code base (Carl's 
code base is in a very good shape, so don't take me wrong), and using 
this we would close the most fundamental missing parts in R3. There 
are around 5-8 topics that need to be addressed. Andreas and I just 
had a short chat about this this week.

R3 gives us the chance to use one technology on a broad range of 
systems. I don't say the same code, but the same technology.

There are several levels of work that can be scaled up. The base 
layer stuff, that's the C & D level.

Than we have fundamental frameworks and libs like R3-GUI etc. this 
is a mix of Rebol code and enhancements on the C/D level.

Than we have the product level, that's what's visible and keeps the 
fire burning. Spitting out cool applications in a fast rate is key. 
I see several markets to address: B2B tools, mostly more effort to 
develop but long lasting and big money. Consumer or Internet market 
applications. More low cost but high volume stuff.

And mobile things. Whatever app is missing today I don't know. I 
can imainge some cool B2B mobile apps, that really help.

Regarding the crowd funding idea, yes, it's appealing. The promise 
would be: You get a complete vertical technology stack to fund your 
next company or app on.

That's it. Take the assambly we did and use it to be 20 times more 
productive than anyone else.

Does anyone know how to reach Brian Tiffing nowadays?  the email 
given here isn't valid anymore!

have you tried SO ?